Devices and Methods for Processing Inputs Using Gesture Recognizers

ABSTRACT

An electronic device displays, on a display, a user interface of an application. The user interface includes a plurality of views arranged in a view hierarchy that defines a first relationship between a first view and a second view. The first view includes a first gesture recognizer, and the second view includes a second gesture recognizer. The device detects, via the input device, an input at a first location that corresponds to the displayed user interface, and processes the input using a gesture recognition hierarchy that includes the first gesture recognizer and the second gesture recognizer. A second relationship between the first gesture recognizer and the second gesture recognizer is determined based on the first relationship between the first view and the second view in the view hierarchy.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/427,203, filed May 30, 2019, which claims priority to U.S.Provisional Patent Application No. 62/679,970, filed Jun. 3, 2018, whichare hereby incorporated by reference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with input devices such astouch-sensitive surfaces, including but not limited to electronicdevices that use gesture recognition techniques to process inputs.

BACKGROUND

Input devices such as touch-sensitive surfaces are widely used toprovide input to electronic devices to manipulate user interfaces andobjects therein on a display. But conventional methods for performingthese manipulations are cumbersome, inefficient, and limited. In somecases, conventional methods of processing inputs are limited infunctionality with respect to the complexity and number of inputs thatcan be recognized. In some cases, conventional methods of processinginputs impose increased computational load on the electronic device asthe complexity and number of inputs that must be recognized increases.In addition, conventional methods take longer than necessary, therebywasting energy. This latter consideration is particularly important inbattery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with improvedmethods and interfaces for processing inputs and recognizing gestures.Such methods and interfaces optionally complement or replaceconventional methods for processing inputs and recognizing gestures.Such methods and interfaces reduce the number, extent, and/or nature ofthe inputs from a user and produce a more efficient human-machineinterface. For battery-operated devices, such methods and interfacesconserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with an input device. The method includes detecting aninput via the input device, and, in response to detecting the input,monitoring the input using a gesture recognizer. The gesture recognizerincludes a plurality of component gesture recognizers that definerequirements for recognition of a gesture. A first component gesturerecognizer from the plurality of component gesture recognizers defines afirst requirement for recognition of the gesture, and a second componentgesture recognizer from the plurality of component gesture recognizersdefines a second requirement for recognition of the gesture. The methodincludes, in accordance with a determination that the input satisfiesfirst gesture recognition criteria that include the first requirement ofthe first component gesture recognizer and the second requirement of thesecond component gesture recognizer, recognizing a first gesture usingthe gesture recognizer.

In accordance with some embodiments, a method is performed at anelectronic device with a display and an input device. The methodincludes displaying, on the display, a user interface of an application.The user interface includes a plurality of views arranged in a viewhierarchy. The view hierarchy defines a first relationship between afirst view and a second view. The first view includes a first gesturerecognizer, and the second view includes a second gesture recognizer.The method includes detecting, via the input device, an input at a firstlocation that corresponds to the displayed user interface, andprocessing the input using a gesture recognition hierarchy that includesthe first gesture recognizer and the second gesture recognizer. A secondrelationship between the first gesture recognizer and the second gesturerecognizer is determined based on the first relationship between thefirst view and the second view in the view hierarchy.

In accordance with some embodiments, a method is performed at anelectronic device with an input device. The method includes detecting aninput via the input device, and, in response to detecting the input,monitoring the input using a gesture recognition tree having a pluralityof nodes. Each respective node of the gesture recognition treecorresponds to a respective gesture recognizer or a respective componentgesture recognizer, and one or more nodes include one or more parametersthat describe the input. Monitoring the input using the gesturerecognition tree includes: processing the input using a first node ofthe plurality of nodes, including determining a value of a firstparameter of the one or more parameters; conveying the first parameterfrom the first node to a second node of the plurality of nodes; andprocessing the input using the second node, including determining, basedon the first parameter, whether the input satisfies a gesturerecognition requirement defined by the second node.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensities of contacts with the touch-sensitive surface,optionally one or more tactile output generators, one or moreprocessors, and memory storing one or more programs; the one or moreprograms are configured to be executed by the one or more processors andthe one or more programs include instructions for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a computer readable storage medium hasstored therein instructions, which, when executed by an electronicdevice with a display, a touch-sensitive surface, optionally one or moresensors to detect intensities of contacts with the touch-sensitivesurface, and optionally one or more tactile output generators, cause thedevice to perform or cause performance of the operations of any of themethods described herein. In accordance with some embodiments, agraphical user interface on an electronic device with a display, atouch-sensitive surface, optionally one or more sensors to detectintensities of contacts with the touch-sensitive surface, optionally oneor more tactile output generators, a memory, and one or more processorsto execute one or more programs stored in the memory includes one ormore of the elements displayed in any of the methods described herein,which are updated in response to inputs, as described in any of themethods described herein. In accordance with some embodiments, anelectronic device includes: a display, a touch-sensitive surface,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, and optionally one or more tactile outputgenerators; and means for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, an information processing apparatus, for use in anelectronic device with a display, a touch-sensitive surface, optionallyone or more sensors to detect intensities of contacts with thetouch-sensitive surface, and optionally one or more tactile outputgenerators, includes means for performing or causing performance of theoperations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, optionally one or more tactile outputgenerators, optionally one or more device orientation sensors, andoptionally an audio system, are provided with improved methods andinterfaces for processing inputs and recognizing gestures, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceconventional methods for processing inputs and recognizing gestures.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 4C-4E illustrate examples of dynamic intensity thresholds inaccordance with some embodiments.

FIGS. 5A-5Q illustrate example gesture recognizers for processing inputs(such as touch inputs) and their operation in accordance with someembodiments.

FIGS. 6A-6C illustrate examples of gesture recognition hierarchiesgenerated from view hierarchies of views in a user interface inaccordance with some embodiments.

FIGS. 7A-7E are flow diagrams for processing inputs using gesturerecognizers assembled from component gesture recognizers in accordancewith some embodiments.

FIGS. 8A-8C are flow diagrams for generating gesture recognitionhierarchies from view hierarchies of views in a user interface inaccordance with some embodiments.

FIGS. 9A-9B are flow diagrams for processing inputs using gesturerecognizers to which values of parameters that describe the inputs havebeen associated in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Many electronic devices have graphical user interface and input devices,such as touch-sensitive surfaces, for receiving inputs by a user. As thenumber and complexity of input gestures increases, processing inputs andrecognizing such gestures becomes more difficult and imposes greatercomputational loads on electronic devices that use conventional gesturerecognition techniques. The embodiments disclosed herein provide moreefficient ways for an electronic device to process inputs and recognizegestures (e.g., using modular gesture recognizers that divide largersets of input processing requirements into smaller subsets).

Below, FIGS. 1A-1B, 2, and 3 show example devices. FIGS. 4A-4Billustrate example user interfaces for example devices on which theembodiments disclosed herein are implemented. FIGS. 5A-5Q illustrateexample gesture recognizers for processing inputs (such as touch inputs)and their operation. FIGS. 6A-6C illustrate examples of gesturerecognition hierarchies generated from view hierarchies of views in auser interface. FIGS. 7A-7E illustrate a flow diagram of a method ofprocessing inputs using gesture recognizers assembled from componentgesture recognizers. FIGS. 8A-8C illustrate a flow diagram of a methodof generating gesture recognition hierarchies from view hierarchies ofviews in a user interface. FIGS. 9A-9B illustrate a flow diagram of amethod of processing inputs using gesture recognizers to which values ofparameters that describe the inputs have been associated. The gesturerecognizers, view hierarchies, and gesture recognition hierarchies inFIGS. 5A-5Q and 6A-6C are used to illustrate the processes in FIGS.7A-7E, 8A-8C, and 9A-9B.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensities of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user. Using tactile outputs toprovide haptic feedback to a user enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, a tactile output pattern specifies characteristicsof a tactile output, such as the amplitude of the tactile output, theshape of a movement waveform of the tactile output, the frequency of thetactile output, and/or the duration of the tactile output.

When tactile outputs with different tactile output patterns aregenerated by a device (e.g., via one or more tactile output generatorsthat move a moveable mass to generate tactile outputs), the tactileoutputs may invoke different haptic sensations in a user holding ortouching the device. While the sensation of the user is based on theuser's perception of the tactile output, most users will be able toidentify changes in waveform, frequency, and amplitude of tactileoutputs generated by the device. Thus, the waveform, frequency andamplitude can be adjusted to indicate to the user that differentoperations have been performed. As such, tactile outputs with tactileoutput patterns that are designed, selected, and/or engineered tosimulate characteristics (e.g., size, material, weight, stiffness,smoothness, etc.); behaviors (e.g., oscillation, displacement,acceleration, rotation, expansion, etc.); and/or interactions (e.g.,collision, adhesion, repulsion, attraction, friction, etc.) of objectsin a given environment (e.g., a user interface that includes graphicalfeatures and objects, a simulated physical environment with virtualboundaries and virtual objects, a real physical environment withphysical boundaries and physical objects, and/or a combination of any ofthe above) will, in some circumstances, provide helpful feedback tousers that reduces input errors and increases the efficiency of theuser's operation of the device. Additionally, tactile outputs are,optionally, generated to correspond to feedback that is unrelated to asimulated physical characteristic, such as an input threshold or aselection of an object. Such tactile outputs will, in somecircumstances, provide helpful feedback to users that reduces inputerrors and increases the efficiency of the user's operation of thedevice.

In some embodiments, a tactile output with a suitable tactile outputpattern serves as a cue for the occurrence of an event of interest in auser interface or behind the scenes in a device. Examples of the eventsof interest include activation of an affordance (e.g., a real or virtualbutton, or toggle switch) provided on the device or in a user interface,success or failure of a requested operation, reaching or crossing aboundary in a user interface, entry into a new state, switching of inputfocus between objects, activation of a new mode, reaching or crossing aninput threshold, detection or recognition of a type of input or gesture,etc. In some embodiments, tactile outputs are provided to serve as awarning or an alert for an impending event or outcome that would occurunless a redirection or interruption input is timely detected. Tactileoutputs are also used in other contexts to enrich the user experience,improve the accessibility of the device to users with visual or motordifficulties or other accessibility needs, and/or improve efficiency andfunctionality of the user interface and/or the device. Tactile outputsare optionally accompanied with audio outputs and/or visible userinterface changes, which further enhance a user's experience when theuser interacts with a user interface and/or the device, and facilitatebetter conveyance of information regarding the state of the userinterface and/or the device, and which reduce input errors and increasethe efficiency of the user's operation of the device.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds to userinterface objects. As used herein, the term “affordance” refers to auser-interactive graphical user interface object (e.g., a graphical userinterface object that is configured to respond to inputs directed towardthe graphical user interface object). Examples of user-interactivegraphical user interface objects include, without limitation, a button,slider, icon, selectable menu item, switch, hyperlink, or other userinterface control.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based on hapticand/or tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In some embodiments, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In some embodiments, projected mutual capacitance sensingtechnology is used, such as that found in the iPhone®, iPod Touch®, andiPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. In someembodiments, tactile output generator(s) 167 include one or moreelectroacoustic devices such as speakers or other audio componentsand/or electromechanical devices that convert energy into linear motionsuch as a motor, solenoid, electroactive polymer, piezoelectricactuator, electrostatic actuator, or other tactile output generatingcomponent (e.g., a component that converts electrical signals intotactile outputs on the device). Tactile output generator(s) 167 receivetactile feedback generation instructions from haptic feedback module 133and generates tactile outputs on device 100 that are capable of beingsensed by a user of device 100. In some embodiments, at least onetactile output generator is collocated with, or proximate to, atouch-sensitive surface (e.g., touch-sensitive display system 112) and,optionally, generates a tactile output by moving the touch-sensitivesurface vertically (e.g., in/out of a surface of device 100) orlaterally (e.g., back and forth in the same plane as a surface of device100). In some embodiments, at least one tactile output generator sensoris located on the back of device 100, opposite touch-sensitive displaysystem 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled with peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled with an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch-screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes varioussoftware components for performing various operations related todetection of contact (e.g., by a finger or by a stylus), such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts or stylus contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

In some embodiments, detecting a finger tap gesture depends on thelength of time between detecting the finger-down event and the finger-upevent, but is independent of the intensity of the finger contact betweendetecting the finger-down event and the finger-up event. In someembodiments, a tap gesture is detected in accordance with adetermination that the length of time between the finger-down event andthe finger-up event is less than a predetermined value (e.g., less than0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensityof the finger contact during the tap meets a given intensity threshold(greater than a nominal contact-detection intensity threshold), such asa light press or deep press intensity threshold. Thus, a finger tapgesture can satisfy particular input criteria that do not require thatthe characteristic intensity of a contact satisfy a given intensitythreshold in order for the particular input criteria to be met. Forclarity, the finger contact in a tap gesture typically needs to satisfya nominal contact-detection intensity threshold, below which the contactis not detected, in order for the finger-down event to be detected. Asimilar analysis applies to detecting a tap gesture by a stylus or othercontact. In cases where the device is capable of detecting a finger orstylus contact hovering over a touch sensitive surface, the nominalcontact-detection intensity threshold optionally does not correspond tophysical contact between the finger or stylus and the touch sensitivesurface.

The same concepts apply in an analogous manner to other types ofgestures. For example, a swipe gesture, a pinch gesture, a depinchgesture, and/or a long press gesture are optionally detected based onthe satisfaction of criteria that are either independent of intensitiesof contacts included in the gesture, or do not require that contact(s)that perform the gesture reach intensity thresholds in order to berecognized. For example, a swipe gesture is detected based on an amountof movement of one or more contacts; a pinch gesture is detected basedon movement of two or more contacts towards each other; a depinchgesture is detected based on movement of two or more contacts away fromeach other; and a long press gesture is detected based on a duration ofthe contact on the touch-sensitive surface with less than a thresholdamount of movement. As such, the statement that particular gesturerecognition criteria do not require that the intensity of the contact(s)meet a respective intensity threshold in order for the particulargesture recognition criteria to be met means that the particular gesturerecognition criteria are capable of being satisfied if the contact(s) inthe gesture do not reach the respective intensity threshold, and arealso capable of being satisfied in circumstances where one or more ofthe contacts in the gesture do reach or exceed the respective intensitythreshold. In some embodiments, a tap gesture is detected based on adetermination that the finger-down and finger-up event are detectedwithin a predefined time period, without regard to whether the contactis above or below the respective intensity threshold during thepredefined time period, and a swipe gesture is detected based on adetermination that the contact movement is greater than a predefinedmagnitude, even if the contact is above the respective intensitythreshold at the end of the contact movement. Even in implementationswhere detection of a gesture is influenced by the intensity of contactsperforming the gesture (e.g., the device detects a long press morequickly when the intensity of the contact is above an intensitythreshold or delays detection of a tap input when the intensity of thecontact is higher), the detection of those gestures does not requirethat the contacts reach a particular intensity threshold so long as thecriteria for recognizing the gesture can be met in circumstances wherethe contact does not reach the particular intensity threshold (e.g.,even if the amount of time that it takes to recognize the gesturechanges).

Contact intensity thresholds, duration thresholds, and movementthresholds are, in some circumstances, combined in a variety ofdifferent combinations in order to create heuristics for distinguishingtwo or more different gestures directed to the same input element orregion so that multiple different interactions with the same inputelement are enabled to provide a richer set of user interactions andresponses. The statement that a particular set of gesture recognitioncriteria do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the particular gesturerecognition criteria to be met does not preclude the concurrentevaluation of other intensity-dependent gesture recognition criteria toidentify other gestures that do have a criteria that is met when agesture includes a contact with an intensity above the respectiveintensity threshold. For example, in some circumstances, first gesturerecognition criteria for a first gesture—which do not require that theintensity of the contact(s) meet a respective intensity threshold inorder for the first gesture recognition criteria to be met—are incompetition with second gesture recognition criteria for a secondgesture—which are dependent on the contact(s) reaching the respectiveintensity threshold. In such competitions, the gesture is, optionally,not recognized as meeting the first gesture recognition criteria for thefirst gesture if the second gesture recognition criteria for the secondgesture are met first. For example, if a contact reaches the respectiveintensity threshold before the contact moves by a predefined amount ofmovement, a deep press gesture is detected rather than a swipe gesture.Conversely, if the contact moves by the predefined amount of movementbefore the contact reaches the respective intensity threshold, a swipegesture is detected rather than a deep press gesture. Even in suchcircumstances, the first gesture recognition criteria for the firstgesture still do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the first gesturerecognition criteria to be met because if the contact stayed below therespective intensity threshold until an end of the gesture (e.g., aswipe gesture with a contact that does not increase to an intensityabove the respective intensity threshold), the gesture would have beenrecognized by the first gesture recognition criteria as a swipe gesture.As such, particular gesture recognition criteria that do not requirethat the intensity of the contact(s) meet a respective intensitythreshold in order for the particular gesture recognition criteria to bemet will (A) in some circumstances ignore the intensity of the contactwith respect to the intensity threshold (e.g. for a tap gesture) and/or(B) in some circumstances still be dependent on the intensity of thecontact with respect to the intensity threshold in the sense that theparticular gesture recognition criteria (e.g., for a long press gesture)will fail if a competing set of intensity-dependent gesture recognitioncriteria (e.g., for a deep press gesture) recognize an input ascorresponding to an intensity-dependent gesture before the particulargesture recognition criteria recognize a gesture corresponding to theinput (e.g., for a long press gesture that is competing with a deeppress gesture for recognition).

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions (e.g., instructions used by haptic feedbackcontroller 161) to produce tactile outputs using tactile outputgenerator(s) 167 at one or more locations on device 100 in response touser interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages, and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (sometimesreferred to simply as an “event” or “input event”) (e.g., a user touchon touch-sensitive display system 112, as part of a multi-touch gesture,or a movement of a touch across touch-sensitive display system 112, or apress of a mouse button, etc.). Event information for an input (e.g., atouch) may include one or more of: a location, timestamp, direction, andspeed of the input. Peripherals interface 118 transmits information itreceives from I/O subsystem 106 (e.g., from touch-sensitive displaysystem 112, one or more sensor(s) 164, 165, and/or one or more inputdevices 350, 355) or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display system112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

While a view is often thought of as being a window or other portion of auser interface, more technically a view is the portion of an applicationthat manages a particular area or region of the application's userinterface. A view is typically implemented as an instance of aparticular class, or one of its subclasses, and manages a rectangulararea in an application window. Thus, a view is an object having anassociated display region or user interface portion, and also one ormore computer programs, sometimes called “methods,” associated with theclass of which the view is an instance. Views are responsible fordrawing content, handling multitouch events, and managing the layout ofany subviews. Drawing content involves using various graphicstechnologies to draw shapes, images, and text inside a view'srectangular area. A view responds to touch events in its rectangulararea either by using gesture recognizers or by handling touch eventsdirectly. In the view hierarchy, parent views are responsible forpositioning and sizing their child views and can do so dynamically. Thisability to modify child views dynamically enables views to adjust tochanging conditions, such as interface rotations and animations.

Views can be viewed as building blocks that a programmer or applicationdeveloper uses to construct the user interface of an application. Ratherthan use one view to present all content for the application, severalviews are typically used to build a view hierarchy. Each view in thehierarchy presents a particular portion of the application's userinterface and is often optimized for a specific type of content. Forexample, an application can have distinct views specifically forpresenting images, text and other types of content.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such asapplication-independent software module 195 (e.g., a user interface kit)or a higher level object from which application 136-1 inherits methodsand other properties. In some embodiments, a respective event handler190 includes one or more of: data updater 176, object updater 177, GUIupdater 178, and/or event data 179 received from event sorter 170. Eventhandler 190 optionally utilizes or calls data updater 176, objectupdater 177 or GUI updater 178 to update the application internal state192. Alternatively, one or more of the application views 191 includesone or more respective event handlers 190. Also, in some embodiments,one or more of data updater 176, object updater 177, and GUI updater 178are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes a plurality ofcomponent event recognizers 181. In some embodiments, the componentevent recognizers 181 used to form an event recognizer 180 are providedby application-independent software module 195.

A respective component gesture recognizer 181 of an event recognizer 180includes component event recognizer-specific code 182, which optionallyincludes event definitions 184. Component gesture recognizer 181 alsoincludes state/phase information 185 and one or more ports 187. In someembodiments, component event recognizer 181 also includes one or moreparameter values 186.

Component event recognizer 181 receives event information from port187-1. The event information includes information about a sub-event, forexample, a touch or a touch movement. Depending on the sub-event, theevent information also includes additional information, such as locationof the sub-event. When the sub-event concerns motion of a touch, theevent information optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Component event recognizer-specific code 182 is used to compare theevent information to predefined event or sub-event definitions and,based on the comparison, determines an event or sub-event, or determinesor updates the state of an event or sub-event. In some embodiments,component event recognizer-specific code 182 includes event definitions184. Event definitions 184 contain definitions of requirements that mustbe satisfied in order for an event recognizer 180 to recognize the event(or gesture) defined by its component event recognizers 181 (e.g., alocation requirement, a minimum and/or maximum movement requirement, aminimum or maximum timing requirement, an intensity thresholdrequirement, etc.). In some embodiments, a requirement is associatedwith a particular sub-event including, for example, touch begin, touchend, touch stationary, touch movement, touch cancellation, and multipletouching. In some embodiments, the event definitions 184 also includeinformation for (e.g., identifying) one or more associated eventhandlers 190.

A respective component event recognizer 181 also includes a state/phase185, which indicates the state of a state machine for the respectivecomponent event recognizer; state/phase 185 can have various statevalues, such as “event possible,” “event active,” “event ended”, “eventfailed” and others. When a respective component event recognizer 181 ofa respective event recognizer 180 determines that a respective sub-eventdoes not match the event definitions 184, the respective component eventrecognizer 181 enters the “failed” state, which causes the respectiveevent recognizer 180 to enter an event impossible or event failed state,after which it disregards subsequent sub-events of the touch-basedgesture. In this situation, other event recognizers, if any, that remainactive for the hit view continue to track and process sub-events of anongoing touch-based gesture.

In some embodiments, a respective component event recognizer 181includes a plurality of ports 187 that indicate how the event deliverysystem should perform sub-event delivery to component event recognizers181 in actively involved event recognizers 180. In some embodiments,ports 187 define the relationships (e.g., the connections, and thus theflow of information) of component event recognizers in a gesturerecognition tree structure. In some embodiments, a respective componentevent recognizer includes one or more parameter values 186 that storevalues of different properties from earlier-received input events orsub-events of a touch input, for comparison with later-received inputevents or sub-events. For example, a component event recognizer includesan initial location parameter that stores the initial location of atouch input as identified from the earliest-received input event for thetouch input, for comparison with current locations of the touch input asidentified from later-received input events to determine whether thetouch input has moved across the touch-sensitive surface, and by howmuch.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoand music player module 152. In some embodiments, object updater 177creates and updates objects used in application 136-1. For example,object updater 177 creates a new user-interface object or updates theposition of a user-interface object. GUI updater 178 updates the GUI.For example, GUI updater 178 prepares display information and sends itto graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In these embodiments, as wellas others described below, a user is enabled to select one or more ofthe graphics by making a gesture on the graphics, for example, with oneor more fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204 (sometimes called home button 204), push button 206 forpowering the device on/off and locking the device, volume adjustmentbutton(s) 208, Subscriber Identity Module (SIM) card slot 210, head setjack 212, and docking/charging external port 124. Push button 206 is,optionally, used to turn the power on/off on the device by depressingthe button and holding the button in the depressed state for apredefined time interval; to lock the device by depressing the buttonand releasing the button before the predefined time interval haselapsed; and/or to unlock the device or initiate an unlock process. Insome embodiments, device 100 also accepts verbal input for activation ordeactivation of some functions through microphone 113. Device 100 also,optionally, includes one or more contact intensity sensors 165 fordetecting intensities of contacts on touch-sensitive display system 112and/or one or more tactile output generators 167 for generating tactileoutputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) for wireless communication(s), such        as cellular and Wi-Fi signals;    -   Time;    -   a Bluetooth indicator;    -   a Battery status indicator;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, labeled            “Music;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, other labels are, optionally, used forvarious application icons. In some embodiments, a label for a respectiveapplication icon includes a name of an application corresponding to therespective application icon. In some embodiments, a label for aparticular application icon is distinct from a name of an applicationcorresponding to the particular application icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. In someembodiments, the examples that follow are carried out using inputs ontouch screen display 112 (where the touch sensitive surface and thedisplay are combined). Alternatively, in some embodiments, the devicedetects inputs on a touch-sensitive surface that is separate from thedisplay, as shown in FIG. 4B. In some embodiments, the touch-sensitivesurface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B)that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or120 ms, depending on the magnitude of the second intensity threshold,with the delay time increasing as the second intensity thresholdincreases). This delay time helps to avoid accidental recognition ofdeep press inputs. As another example, for some “deep press” inputs,there is a reduced-sensitivity time period that occurs after the time atwhich the first intensity threshold is met. During thereduced-sensitivity time period, the second intensity threshold isincreased. This temporary increase in the second intensity thresholdalso helps to avoid accidental deep press inputs. For other deep pressinputs, the response to detection of a deep press input does not dependon time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Example factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 4C illustrates a dynamic intensity threshold 480 thatchanges over time based in part on the intensity of touch input 476 overtime. Dynamic intensity threshold 480 is a sum of two components, firstcomponent 474 that decays over time after a predefined delay time p1from when touch input 476 is initially detected, and second component478 that trails the intensity of touch input 476 over time. The initialhigh intensity threshold of first component 474 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 476 provides sufficient intensity.Second component 478 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of in a touch input. In someembodiments, when touch input 476 satisfies dynamic intensity threshold480 (e.g., at point 481 in FIG. 4C), the “deep press” response istriggered.

FIG. 4D illustrates another dynamic intensity threshold 486 (e.g.,intensity threshold I_(D)). FIG. 4D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 4D, although touch input 484 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 482. Also in FIG. 4D, dynamic intensity threshold 486decays over time, with the decay starting at time 488 after a predefineddelay time p1 has elapsed from time 482 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 4E illustrate yet another dynamic intensity threshold 492 (e.g.,intensity threshold I_(D)). In FIG. 4E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 490 is initially detected. Concurrently,dynamic intensity threshold 492 decays after the predefined delay timep1 has elapsed from when touch input 490 is initially detected. So adecrease in intensity of touch input 490 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 490, without releasing touch input 490,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 494) even when the intensity of touch input 490 is belowanother intensity threshold, for example, the intensity threshold I_(L).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, (optionally) one or more tactileoutput generators for generating tactile outputs, and (optionally) oneor more sensors to detect intensities of contacts with thetouch-sensitive surface.

FIGS. 5A-5Q illustrate example gesture recognizers for processing inputs(such as touch inputs) and their operation in accordance with someembodiments. FIGS. 6A-6C illustrate examples of gesture recognitionhierarchies (sometimes called gesture recognition trees) generated froma view hierarchy of views in a user interface based on received inputs.The gesture recognizers, view hierarchies, and gesture recognitionhierarchies in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 7A-7E, 8A-8C, and9A-9B. For convenience of explanation, some of the embodiments will bediscussed with reference to operations performed on a device with atouch-sensitive display system 112 in response to receiving inputs onthe touch-sensitive display system 112. In such embodiments, the focusselector is, optionally: a respective finger or stylus contact, arepresentative point corresponding to a finger or stylus contact (e.g.,a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112. However, analogous operationsare, optionally, performed on a device with a display 450 and a separatetouch-sensitive surface 451 in response to receiving inputs on thetouch-sensitive surface 451, or on a device with a keyboard/mouse 350 inresponse to receiving inputs via the mouse.

FIGS. 5A-5Q illustrate example gesture recognizers and their operationwhile processing inputs in accordance with some embodiments.

FIGS. 5A-5F illustrate an example tap gesture recognizer 500 and itsoperation while processing inputs. FIG. 5A shows that tap gesturerecognizer 500 includes a plurality of component gesture recognizersthat define requirements for recognition of a tap gesture, arranged in atree structure. The plurality of component gesture recognizers of tapgesture recognizer 500 include:

-   -   spatial event listener 502, which requires that the location of        a touch input received on the touch-sensitive surface be known        by monitoring for input events that include location        information;    -   maximum duration component 504, which requires that an amount of        time that the touch input is maintained on the touch-sensitive        surface be less than a predefined threshold amount of time        T_(th); and    -   distance component 506, which requires that an amount of        movement of the touch input across the touch-sensitive surface        (if any) be less than a predefined threshold amount of movement        D_(max_th).

Tap gesture recognizer 500 also includes pause-for-predecessor component508, which is optionally used to require that any gesture recognizerhaving priority over tap gesture recognizer 500 (e.g., any predecessorgesture recognizer) fail in order for a tap gesture to be recognized.Stated another way, pause-for-predecessor 508 prevents tap gesturerecognizer 500 from succeeding while any predecessor gesture recognizerof tap gesture recognizer 500 is active, in certain situations describedherein.

In addition, tap gesture recognizer 500 includes two gating combiners.Gating combiner 510 is controlled by pause-for-predecessor component 508and maximum duration component 504. When maximum duration component 504is in a failed state (e.g., an input has exceeded a predefined thresholdamount of time, sometimes called the maximum threshold duration), gatingcombiner 510 is in a failed state. When maximum duration component 504is in a state other than a failed state (e.g., an active state), gatingcombiner 510 passes through the input processing results (e.g., stateand parameter values) received from pause-for-predecessor component 508.Similarly, gating combiner 512 is controlled by gating combiner 510 anddistance component 506. When distance component 506 is in a failedstate, gating combiner 512 is in a failed state. When distance component506 is in a state other than a failed state (e.g., an active state),gating combiner 512 passes through the input processing results (e.g.,state and parameter values) received from gating combiner 510. Moregenerally, when the right-hand-side child component gesture recognizerof a gating combiner is in the failed state, the gating combiner is inthe failed state, and when the right-hand-side child component gesturerecognizer of the gating combiner is in a state other than the failedstate, the gating combiner passes through the input processing resultsreceived from its left-hand-side child component gesture recognizer.

While FIGS. 5A-5F show only pause for predecessor component 508 having aspatial event listener 502 as a child component, in some embodiments,max duration component 504 and/or distance component 506 also havespatial event listeners (e.g., additional instances of spatial eventlistener 502) as a child component, or alternatively have input portsthat are also coupled to spatial event listener 502.

FIG. 5B illustrates receipt of an input event at tap gesture recognizer500 (e.g., from event dispatcher module 174) in response to a touchinput being received at the device. In particular, the input event isreceived at gating combiner 512, which is the root node of tap gesturerecognizer 500. Input events received at a gesture recognizer aresometimes described as “flowing down the tree”—that is, the input eventsare conveyed from each respective node at a higher level in the tree toits associated nodes at the next lower level in the tree. In some cases,a combiner that has multiple child nodes conveys input events to itschild nodes based on predefined information conveyance rules, asdescribed in more detail herein. In the example shown in FIG. 5B, gatingcombiner 512 conveys the input event to both of its child nodes, gatingcombiner 510 and distance component 506. Similarly, gating combiner 510conveys the input event to both of its child nodes,pause-for-predecessor component 508 and maximum duration component 504.In addition, pause-for-predecessor component 508 conveys the input eventto its child node, spatial event listener 502.

FIG. 5C illustrates the results of processing the input event shown inFIG. 5B by the component gesture recognizers in tap gesture recognizer500. The results of processing an input event received at a gesturerecognizer are sometimes described as being passed “up the tree”—thatis, the input events are conveyed from each respective node at a lowerlevel in the tree to its associated node at the next higher level in thetree. A respective node at a higher level in the tree that has multipleassociated nodes at the next lower level in the tree determines its ownresults based on the combination of results from its multiple associatednodes.

In the example shown in FIGS. 5B-5C, the received input event is a“spatial event,” that is, an event that includes (information about) thelocation of the received touch input, and includes the initial locationp_(i) of the touch input. The received input event is also the firstinput event for a newly-received touch input, and accordingly has aphase value of “touch begin” and an initial timestamp t_(i) indicatingthe time at which the touch input was first received or detected. Asshown in FIG. 5C, spatial event listener 502 has identified the inputevent as a spatial event for an ongoing touch input (as indicated by the“touch begin” phase value) and accordingly is in the “active” state.Spatial event listener 502 conveys its current “active” state and thespatial input event to its parent node, pause-for-predecessor 508.

Pause-for-predecessor component 508, in the example shown in FIG. 5C, isin the “active” state because tap gesture recognizer 500 has nopredecessor gesture recognizer that is active (either because no othergesture recognizer has priority over tap gesture recognizer 500, orbecause every gesture recognizer having priority over tap gesturerecognizer 500 has failed). Pause-for-predecessor component 508 conveysits current “active” state and the spatial input event to its parentnode, gating combiner 510. In some embodiments, where another gesturerecognizer (such as a double-tap gesture recognizer) has priority overtap gesture recognizer 500 (e.g., by using an exclusive combiner, asdescribed herein), tap gesture recognizer 500 receives an indication,included with or in addition to the input event, as to whether apredecessor gesture recognizer is active. In such cases,pause-for-predecessor component 508 outputs an indication thatrecognition of a tap gesture by tap gesture recognizer 500 should besuspended or “paused” until an indication is received that thepredecessor gesture recognizer has failed. If no such indication isreceived, tap gesture recognizer remains in the suspended state and doesnot successfully recognize a tap gesture (e.g., even though, in the caseof a double-tap gesture recognizer having priority over the tap gesturerecognizer and recognizing a double-tap gesture, the first tap gestureof the double-tap gesture would have been recognized by the tap gesturerecognizer).

Maximum duration component 504 has identified the current timestampt_(i) of the input event. In addition, maximum duration component 504has identified the input event as an event having a phase value of“touch begin.” Accordingly, maximum duration component 504 has storedthe identified current timestamp t_(i) as the initial timestampassociated with the touch input. Maximum duration component 504 uses theinitial timestamp to determine whether the touch input has remained onthe touch-sensitive surface for more than the predefined thresholdamount of time T_(th). At initial detection of the touch input, when thetimestamp is the initial timestamp t_(i), the touch input has not yetremained on the touch-sensitive surface for more than the predefinedthreshold amount of time T_(th), so maximum duration component 504 is inthe “active” state. Maximum duration component 504 conveys its current“active” state to its parent node, gating combiner 510.

Gating combiner 510, as described above, is controlled bypause-for-predecessor component 508 and maximum duration component 504.Because maximum duration component 504 is in the “active” state and thusnot in the “failed” state, gating combiner 510 passes through the inputprocessing results received from pause-for-predecessor component 508.Accordingly, gating combiner 510 conveys the “active” state and thespatial event to its parent node, gating combiner 512.

Distance component 506 has identified the current location p_(i) of thetouch input from the input event. In addition, distance component 506has identified the input event as an event having a phase value of“touch begin.” Accordingly, distance component 506 has stored theidentified current location p_(i) as the initial location of the touchinput. In general, distance components use the initial location todetermine whether movement (if any) of a touch input satisfies a minimumamount of movement and/or a maximum amount of movement. In someembodiments, a distance component is used in gesture recognizers thatrequire movement of a touch input to define a minimum threshold amountof movement. In some embodiments, a distance component is used ingesture recognizers that require a limit on the amount of movement of atouch input to define a maximum threshold amount of movement. In someembodiments, both a minimum threshold amount of movement and a maximumthreshold amount of movement can be defined to require that movement ofa touch input be within a predefined range.

In the example shown in FIG. 5C, distance component 506 uses the initiallocation to determine whether the touch input has moved across thetouch-sensitive surface by more than the predefined maximum thresholdamount D_(max_th). At initial detection of the touch input, when thelocation is the initial location p_(i), the touch input has not yetmoved across the touch-sensitive surface, so distance component 506 isin the “active” state. Distance component 506 conveys its current“active” state to its parent node, gating combiner 512.

Gating combiner 512, as described above, is controlled by gatingcombiner 510 and distance component 506. Because distance component 506is in the “active” state and thus not in the “failed” state, gatingcombiner 512 passes through the input processing results received fromgating combiner 510. Accordingly, gating combiner 512 conveys the“active” state and the spatial event received from gating combiner 510.Because gating combiner 512 is the root node of tap gesture recognizer500, the overall state of tap gesture recognizer 500 is the “active”state, and the overall output values of tap gesture recognizer 500 arethose of the spatial event. In some embodiments, the overall state andoutput values of an assembled gesture recognizer (such as tap gesturerecognizer 500) are conveyed by the gesture recognizer to a parent nodeof the gesture recognizer where the gesture recognizer is used as partof another gesture recognizer. For example, as described herein withreference to FIGS. 5G-5L, double-tap gesture recognizer 520 includes anassembled tap gesture recognizer 524 as a component, and thus theoverall state and output values of tap gesture recognizer 524 areconveyed to other components (e.g., repeater 522, FIG. 5G) in double-tapgesture recognizer 520. In some embodiments, the overall state andoutput values of an assembled gesture recognizer are conveyed by thegesture recognizer to a parent node of the gesture recognizer where thegesture recognizer is a child node in a gesture recognition hierarchy.For example, as described herein with reference to FIG. 6A, gesturerecognition hierarchy 640 includes an assembled tap gesture recognizer614 as a child node, and thus the overall state and output values of tapgesture recognizer 614 are conveyed to other components (e.g., exclusivecombiner 642, FIG. 6A) in gesture recognition hierarchy 640. In someembodiments, the overall state and output values of an assembled gesturerecognizer are conveyed by the gesture recognizer to an application thatis executing on the device and that includes the gesture recognizer(e.g., application 136-1, FIG. 1B).

FIG. 5D illustrates an example of successful recognition of a tapgesture. In particular, FIG. 5D illustrates the results of processing asecond input event that is associated with liftoff of the touch inputdescribed with respect to FIGS. 5B-5C with all of the gesturerecognition requirements of tap gesture 500 being satisfied. The secondinput event is received after the (first) input event described withrespect to FIGS. 5B-5C has been received (as shown in FIG. 5B) andprocessed (as shown in FIG. 5C). The second input event is another“spatial event,” but has a phase value of “touch end” and includes thelocation p_(c) of the touch input at the time of liftoff and thetimestamp t_(c) indicating the time of liftoff. As shown in FIG. 5D,spatial event listener 502 has identified the input event as a spatialevent for a completed touch input (as indicated by the “touch end” phasevalue) and accordingly is in the “ended” state. Spatial event listener502 conveys its current “ended” state and the spatial input event to itsparent node, pause-for-predecessor 508.

Pause-for-predecessor component 508, in the example shown in FIG. 5D, isin the “ended” state because tap gesture recognizer 500 has nopredecessor gesture recognizer that is active. Pause-for-predecessorcomponent 508 conveys its current “ended” state and the spatial inputevent to its parent node, gating combiner 510.

Maximum duration component 504 has identified the current timestampt_(c) of the input event. Maximum duration component has compared thecurrent timestamp t_(c) to the stored initial timestamp t_(i) todetermine that the amount of time that touch input has remained on thetouch-sensitive surface (t_(c)−t_(i)) is less than the predefinedthreshold amount of time T_(th). Accordingly, maximum duration component504 has not transitioned to the “failed” state. Instead, maximumduration component 504 has identified the input event as an event havinga phase value of “touch end,” and, having not transitioned to the“failed” state for any reason, has thus transitioned to the “ended”state. Maximum duration component 504 conveys its current “ended” stateto its parent node, gating combiner 510.

Gating combiner 510, as described above, is controlled bypause-for-predecessor component 508 and maximum duration component 504.Because maximum duration component 504 is in the “ended” state and thusnot in the “failed” state, gating combiner 510 passes through the inputprocessing results received from pause-for-predecessor component 508.Accordingly, gating combiner 510 conveys the “ended” state and thespatial event to its parent node, gating combiner 512.

Distance component 506 has identified the current location p_(c) of thetouch input from the input event. Distance component 506 has comparedthe current location p_(c) to the stored initial location p_(i) todetermine that the distance traveled by the touch input (the absolutevalue of p_(c)−p_(i), |p_(c)−p_(i)|) is less than the predefined maximumthreshold distance D_(max,th). Accordingly, distance component 506 hasnot transitioned to the “failed” state. Instead, distance component 506has identified the input event as an event having a phase value of“touch end,” and, having not transitioned to the “failed” state for anyreason, has thus transitioned to the “ended” state. Distance component506 conveys its current “ended” state to its parent node, gatingcombiner 512.

Gating combiner 512, as described above, is controlled by gatingcombiner 510 and distance component 506. Because distance component 506is in the “ended” state and thus not in the “failed” state, gatingcombiner 512 passes through the input processing results received fromgating combiner 510. Accordingly, gating combiner 512 conveys the“ended” state and the spatial event received from gating combiner 510.Because gating combiner 512 is the root node of tap gesture recognizer500, the overall state of tap gesture recognizer 500 is the “ended”state, and the overall output values of tap gesture recognizer 500 arethose of the spatial event. With the transitioning of gating combiner512 to the “ended” state, tap gesture recognizer 500 has successfullyrecognized the touch input as a tap gesture.

FIG. 5E illustrates an example of failure of a tap gesture recognizer500 to recognize a touch input. In particular, FIG. 5E illustrates theresults of processing a third input event that is associated withmovement of the touch input described with respect to FIGS. 5B-5C, andthat is received instead of the second input event described withrespect to FIG. 5D. The third input event is received after the (first)input event described with respect to FIGS. 5B-5C has been received (asshown in FIG. 5B) and processed (as shown in FIG. 5C). The third inputevent is another “spatial event” but has a phase value of “touchmovement” (or, in some embodiments, “touch change”) and includes thecurrent location p_(c) of the touch input and the timestamp t_(c)indicating the time associated with the third input event. As shown inFIG. 5E, spatial event listener 502 has identified the input event as aspatial event for an ongoing touch input (as indicated by the “touchmovement” phase value) and accordingly is in the “active” state. Spatialevent listener 502 conveys its current “active” state and the spatialinput event to pause-for-predecessor 508.

Pause-for-predecessor component 508, in the example shown in FIG. 5D, isin the “active” state because tap gesture recognizer 500 has nopredecessor gesture recognizer that is active. Pause-for-predecessorcomponent 508 conveys its current “active” state and the spatial inputevent to gating combiner 510.

Maximum duration component 504 has identified the current timestampt_(c) of the input event. Maximum duration component has compared thecurrent timestamp t_(c) to the stored initial timestamp t_(i) todetermine that the amount of time that touch input has remained on thetouch-sensitive surface (t_(c)−t_(i)) is less than the predefinedthreshold amount of time T_(th). Accordingly, maximum duration component504 has not transitioned to the “failed” state and, because the inputevent has a phase value of “touch movement” rather than “touch end,”remains in the “active” state. Maximum duration component 504 conveysits current “active” state to gating combiner 510.

Because maximum duration component 504 is in the “active” state and thusnot in the “failed” state, gating combiner 510 passes through the“active” state and the spatial event received from pause-for-predecessorcomponent 508 to gating combiner 512.

Distance component 506 has identified the current location p_(c) of thetouch input and compared the current location p_(c) to the storedinitial location p_(i) to determine that the distance traveled by thetouch input (|p_(c)−p_(i)|) is greater than the predefined maximumthreshold distance D_(max,th). Accordingly, distance component 506 hastransitioned to the “failed” state. Distance component 506 conveys itscurrent “failed” state to gating combiner 512.

Gating combiner 512 is controlled by the “failed” state of distancecomponent 506 such that gating component 512 is also in the “failed”state. Because gating combiner 512 is the root node of tap gesturerecognizer 500, the overall state of tap gesture recognizer 500 is the“failed” state, and no tap gesture is recognized by tap gesturerecognizer 500.

FIG. 5F illustrates another example of failure of tap gesture recognizer500 to recognize a touch input. In particular, FIG. 5F illustrates theresults of processing a fourth input event that is associated with thetouch input described with respect to FIGS. 5B-5C being maintained onthe touch-sensitive surface, and that is received instead of the secondand third input events described with respect to FIGS. 5D-5E. The fourthinput event is received after the (first) input event described withrespect to FIGS. 5B-5C has been received (as shown in FIG. 5B) andprocessed (as shown in FIG. 5C). The fourth input event is another“spatial event” but has a phase value of “touch stationary” and includesthe current location p_(c) of the touch input and the timestamp t_(c)indicating the time associated with the third input event.

Maximum duration component 504 has identified the current timestampt_(c) of the input event and compared the current timestamp t_(c) to thestored initial timestamp t_(i) to determine that the amount of time thattouch input has remained on the touch-sensitive surface (t_(c)−t_(i))has exceeded the predefined threshold amount of time T_(th).Accordingly, maximum duration component 504 has transitioned to the“failed” state. Maximum duration component 504 conveys its current“failed” state to gating combiner 510, which controls gating combiner510 to also be in the “failed” state (e.g., causes gating combiner 510to transition to the “failed” state).

Distance component 506 has identified the current location p_(c) of thetouch input and compared the current location p_(c) to the storedinitial location p_(i) to determine that the distance traveled by thetouch input (|p_(c)−p_(i)|) is less than the predefined maximumthreshold distance D_(max,th). Accordingly, distance component 506 hasnot transitioned to the “failed” state and, because the input event hasa phase value of “touch stationary” rather than “touch end,” remains inthe “active” state. Distance component 506 conveys its current “active”state to gating combiner 512.

Because distance component 506 is in the “active” state and thus not inthe “failed” state, gating combiner 512 passes through the “failed”state and the spatial event received from gating combiner 510. Becausegating combiner 512 is the root node of tap gesture recognizer 500, theoverall state of tap gesture recognizer 500 is the “failed” state, andno tap gesture is recognized by tap gesture recognizer 500. In someembodiments, the passed-through spatial event output by tap gesturerecognizer 500 is ignored because tap gesture recognizer 500 has failed.

FIGS. 5G-5L illustrate an example double-tap gesture recognizer 520 andits operation while processing inputs. FIG. 5G shows that double-tapgesture recognizer 520 includes a plurality of component gesturerecognizers that define requirements for a double-tap gesture,including:

-   -   repeater 522, which requires repeated success of its child        component gesture recognizer or child gesture recognizer of (at        least) a predefined number of times defined by a repeat count        value (“count_(repeat)”), optionally subject to a timeout period        (“T_(timeout)”) such that each additional success must occur        before the amount of time that has elapsed since the most-recent        previous success reaches (or exceeds) the predefined timeout        period; and    -   tap gesture recognizer 524, which is a high-level representation        of the various component gesture recognizers of a tap gesture        recognizer as described herein with reference to example tap        gesture recognizer 500 in FIGS. 5A-5F.

In the example shown in FIG. 5G, repeater 522 requires, in order fordouble-tap gesture recognizer 520 to succeed, recognition of twosuccessful tap gestures (through setting count_(repeat) to a value of“2”) within 0.5 seconds of each other (through setting T_(timeout) to avalue of “0.5 s”). In some embodiments, as shown in FIGS. 5G-5L,repeater 522 uses a first instance 524 a of the tap gesture recognizerto monitor for the first required tap gesture, and a second instance 524b of the tap gesture recognizer to monitor for the second required tapgesture (after the first required tap gesture is recognized). Moregenerally, in some embodiments, a new/different instance of the child(component) gesture recognizer of a repeater is used to monitor for eachsuccessive occurrence of the gesture recognition requirements of thechild (component) gesture recognizer being satisfied. In someembodiments, the repeater in a gesture recognizer reuses a single child(component) gesture recognizer (e.g., a same instance of the child(component) gesture recognizer) by resetting the state(s) and value(s)of the child (component) gesture recognizer each time the gesturerecognition requirements of the child (component) gesture recognizer aresatisfied. In some embodiments, the repeater tracks the number of timesthat its child (component) gesture recognizer has succeeded.

FIG. 5G further illustrates receipt of a first input event (“event₁”) atdouble-tap gesture recognizer 520 (e.g., from event dispatcher module174) in response to a first touch input being received at the device. Inparticular, the first input event is received at repeater 522, which isthe root node of double-tap gesture recognizer 520. Repeater 522 conveysthe first input event to its child node, tap gesture recognizer 524 a.More specifically, because tap gesture recognizer 524 a is itself a treestructure, repeater 522 conveys the first input event to the root nodeof tap gesture recognizer 524 a (e.g., a gating combiner such as gatingcombiner 512, FIG. 5B), which in turn conveys the first input event toother nodes in tap gesture recognizer 524 a (e.g., as described hereinwith reference to FIG. 5B). In some embodiments, repeater 532 adds thefirst instance 524 a of the tap gesture recognizer to double-tap gesturerecognizer 520 in response to receiving the first input event, and thenconveys the first input event to the root node of tap gesture recognizer524 a to processing. In some embodiments, “adding” an instance of afirst gesture recognizer (e.g., the tap gesture recognizer) or a firstcomponent gesture recognizer to a second gesture recognizer (e.g., thedouble-tap gesture recognizer) includes creating or generating aninstance of the first gesture recognizer or first component gesturerecognizer, setting or initializing one or more parameters of thegenerated instance (e.g., setting a threshold value, and/or setting oneor more configuration parameters to control how the generated instanceoperates), and connecting the generated instance to the second gesturerecognizer (e.g., connecting a port of the first gesture recognizer orfirst component gesture recognizer to a port of the second gesturerecognizer).

FIG. 5H illustrates the results of processing the first input eventshown in FIG. 5G by the component gesture recognizers in double-tapgesture recognizer 520. In the example shown in FIG. 5H, the first inputevent has been determined to be a spatial event (e.g., by the spatialevent listener of tap gesture recognizer 524 a). The first input eventdescribes an ongoing touch input (e.g., the first input event has aphase value of “touch begin” or “touch stationary”) and includes thelocation of the received first touch input. Tap gesture recognizer 524 ahas processed the first input event (e.g., as described herein withreference to FIG. 5C) and accordingly has transitioned to the “active”state. In addition, tap gesture recognizer 524 a has conveyed itscurrent “active” state and the first input event (“spatial event₁”) upthe tree to repeater 522.

Repeater 522 includes an input count value (“count_(input)”) 526 thattracks the number of times that tap gesture recognizer 524 (or arespective instance of tap gesture recognizer 524) has succeeded.Because tap gesture recognizer (instance 1) 524 a has not yet succeeded(e.g., tap gesture recognizer 524 a has not yet transitioned to the“ended” state), input count value 526 has a value of zero. In addition,repeater 522 has transitioned to the “active” state in response to thefirst touch input being received (but not yet ended). Repeater 522conveys, as its output, its current “active” state and the first spatialevent (“spatial event”) received from tap gesture recognizer 524 a.Because repeater 522 is the root node of double-tap gesture recognizer520, the overall state of double-tap gesture recognizer 520 is the“active” state, and the overall output values of double-tap gesturerecognizer 520 are those of the first spatial event.

FIG. 5I illustrates the results of processing a second input event(“event₂”) that has been received at double-tap gesture recognizer 520and that is associated with liftoff of the first touch input describedwith respect to FIGS. 5G-5H. The second input event is received afterthe first input event has been received and processed (e.g., asdescribed herein with respect to FIGS. 5G-5H). The second input eventhas been determined to be a spatial event (“spatial event₂”) similar tothe first input event, except that the second input event has a phasevalue of “touch end.” As shown in FIG. 5I, tap gesture recognizer 524 ahas processed the second input event (e.g., as described herein withreference to FIG. 5D) and recognized the first touch input as a firsttap gesture. Tap gesture recognizer 524 a accordingly has transitionedto the “ended” state and has conveyed its current “ended” state and thesecond input event to repeater 522. In accordance with tap gesturerecognizer 524 a successfully recognizing a first tap gesture, repeater522 increases input count value 526 to a value of one.

In some embodiments, after repeater 522 has transitioned to the “active”state in response to a touch input being received, repeater 522 remainsin the “active” state either until tap gesture recognizer 524 (or arespective instance of tap gesture recognizer 524) transitions to the“failed” state, or until tap gesture recognizer 524 has succeeded thepredefined number of times required by repeat count value(“count_(repeat)”). In FIG. 5I, because tap gesture recognizer 524 a hasnot transitioned to the “failed” state, and because only one tap inputhas been detected, repeater 522 remains in the “active” state. Repeater522 conveys, as its output, its current “active” state and the secondspatial event (“spatial event₂”) received from tap gesture recognizer524 a. Accordingly, the overall state of double-tap gesture recognizer520 is the “active” state, and the overall output values of double-tapgesture recognizer 520 are those of the second spatial event.

FIG. 5J illustrates receipt of a third input event (“event₃”) atdouble-tap gesture recognizer 520 in response to a second touch inputbeing received at the device. Because double-tap gesture recognizer 520(and in particular, tap gesture recognizer (instance 1) 524 a) hasrecognized a first tap input, the first instance 524 a of the tapgesture recognizer has been replaced with a second instance 524 b of thetap gesture recognizer (e.g., a second instance of tap gesturerecognizer 500, FIG. 5B). In some embodiments, repeater 532 removes thefirst instance 524 a of the tap gesture recognizer from double-tapgesture recognizer 520 in response to receiving a processed input fromthe first instance 524 a, indicating that a first tap gesture has beenrecognized, and repeater 532 adds a second instance 524 b of the tapgesture recognizer to double-tap gesture recognizer 520 in response toreceiving the third input event. Repeater 522 conveys the third inputevent to tap gesture recognizer (instance 2) 524 b for processing (e.g.,as described herein with reference to FIG. 5C) to determine whether thesecond touch input is a tap gesture.

FIG. 5K illustrates the results of processing the third input eventshown in FIG. 5J by the component gesture recognizers in double-tapgesture recognizer 520. In the example shown in FIGS. 5J-5K, the thirdinput event has been determined to be a spatial event (e.g., by thespatial event listener of tap gesture recognizer 524 b). The third inputevent describes an ongoing touch input (e.g., the third input event hasa phase value of “touch begin” or “touch stationary”) and includes thelocation of the received second touch input and a current timestampt_(c) associated with the third input event. Tap gesture recognizer 524b has processed the third input event (e.g., as described herein withreference to FIG. 5C) and accordingly has transitioned to the “active”state. In addition, tap gesture recognizer 524 b has conveyed itscurrent “active” state and the third input event (“spatial event₃”) torepeater 522. Because tap gesture recognizer (instance 2) 524 b has notyet succeeded (e.g., tap gesture recognizer 524 b has not yettransitioned to the “ended” state), input count value 526 of repeater522 is maintained with a value of one.

In addition, repeater 522 monitors an amount of time that has elapsedsince a time corresponding to the most-recently recognized tap gesture.In some embodiments, repeater 522 monitors the amount of time that haselapsed from a beginning of the touch input that was identified as themost-recently recognized tap gesture (e.g., by identifying and storingthe initial timestamp associated with the “touch begin” event for thattouch input). In some embodiments, repeater 522 monitors the amount oftime that has elapsed from an end of that touch input (e.g., byidentifying and storing the ending timestamp associated with the “touchend” event for that touch input). For example, in FIG. 5K, repeater 522monitors the time that has elapsed from the end of the first tap gesture(“t_(tap1ended)”) that was most-recently successfully recognized by tapgesture recognizer 524 a (FIG. 5I) to the current time associated withthe third input event (“t_(c)”). Because the amount of time that haselapsed from the end of the first tap gesture (“t_(tap1ended)”) to thecurrent time associated with the third input event (“t_(c)”) is lessthan the predefined timeout period (“T_(timeout)”), and because tapgesture recognizer 524 b has transitioned to neither the “ended” statenor the “failed” state, repeater 522 remains in the “active” state.Repeater 522 conveys, as both its own output and as the overall outputof double-tap gesture recognizer 520, its current “active” state and thethird spatial event (“spatial event₃”) received from tap gesturerecognizer 524 b.

FIG. 5L illustrates the results of processing a fourth input event(“event₄”) that has been received at double-tap gesture recognizer 520and that is associated with liftoff of the second touch input describedwith respect to FIGS. 5J-5K. The fourth input event is received afterthe third input event has been received and processed (e.g., asdescribed herein with respect to FIGS. 5J-5K). The fourth input eventhas been determined to be a spatial event (“spatial event₄”) similar tothe third input event, except that the fourth input event has a phasevalue of “touch end.” As shown in FIG. 5L, tap gesture recognizer 524 bhas processed the fourth input event (e.g., as described herein withreference to FIG. 5D) and recognized the second touch input as a secondtap gesture. Tap gesture recognizer 524 b accordingly has transitionedto the “ended” state and has conveyed its current “ended” state and thefourth input event to repeater 522. In accordance with tap gesturerecognizer 524 b successfully recognizing a second tap gesture, repeater522 increases input count value 526 to a value of two.

In addition, the amount of time that has elapsed from the end of thefirst tap gesture (“t_(tap1ended)”) to the end of the second tap gesture(“t_(tap2ended)”) is less than the predefined timeout period(“T_(timeout)”). Because the timing requirement remains satisfied, andbecause tap gesture recognizer 524 b has transitioned to the “ended”state, repeater 522 transitions to the “ended” state. Repeater conveys,as both its own output and as the overall output of double-tap gesturerecognizer 520, its current “ended” state and the fourth spatial event(“spatial event₄”) received from tap gesture recognizer 524 b. Theoutputting of the “ended” state by repeater 522 indicates thatdouble-tap gesture recognizer 520 has successfully recognized adouble-tap gesture.

In some embodiments, if either instance of tap gesture recognizer 524were to have transitioned to the “failed” state, repeater 522 would havetransitioned to the “failed” state, and no double-tap gesture would havebeen recognized. Furthermore, if the end of a second tap gesture had notbeen received before the predefined timeout period (“T_(timeout)”) hadelapsed since the first recognized tap gesture, repeater 522 would havetransitioned to the “failed” state, and no double-tap gesture would havebeen recognized.

FIGS. 5M-5Q illustrate an example (two-input) pinch gesture recognizer530 and its operation while processing inputs. In some embodiments,pinch gesture recognizer 530, or an instance thereof, is included in aparticular view of a user interface, and is used to recognize two-inputpinch gestures performed using touch inputs in the particular view ofthe user interface. FIG. 5M shows that pinch gesture recognizer 530includes a plurality of component gesture recognizer that definerequirements for a pinch gesture, including:

-   -   a first drag component (“drag 1”) 532, which requires that the        location of a touch input received on the touch-sensitive        surface be known by monitoring for input events that include        location information, similar to a spatial event listener,        except that a drag component also monitors an amount of movement        of a touch input; and    -   a second drag component (“drag 2”) 534, which behaves similarly        to first drag component 532 but is a distinct drag component (or        a distinct instance of a drag component) from first drag        component 532.

Pinch gesture recognizer 530 also includes a parallel combiner 536.Parallel combiner 536 controls the conveyance of input events to firstdrag component 532 and second drag component 534. Specifically, parallelcombiner assigns a different touch input to each drag component suchthat each drag component receives and processes input events only forits assigned touch input. The state of parallel combiner 536 isdependent on the respective states of the drag components, and theoutput values of parallel combiner 536 are the output values of the dragcomponents, as described in more detail herein.

In addition, pinch gesture recognizer 530 includes a pinch component538. Pinch component 536 determines a scale (e.g., which is used tocontrol a scale of a displayed user interface or user interface elementwhen a pinch gesture is detected), and optionally a scale velocity(e.g., which is used to continue to adjust the scale of the userinterface or user interface element after a detected pinch gesture hasended).

FIG. 5M further illustrates receipt of two input events at pinch gesturerecognizer 530 (e.g., from event dispatcher module 174) in response tomultiple touch inputs being received at the device. Specifically, pinchgesture recognizer 530 receives a first input event (“event₁”) inresponse to a first received touch input (“input₁”) and a second inputevent (“event₂”) in response to a second received touch input(“input₂”). Pinch component 538, which is the root node of pinch gesturerecognizer 530, receives the input events and conveys both input eventsto parallel combiner 536. Parallel combiner 536 assigns the first touchinput to first drag component 532 and conveys the first input event forthe first touch input to first drag component 532. In addition, parallelcombiner 536 assigns the second touch input to second drag component 532and conveys the second input event for the second touch input to seconddrag component 532.

FIG. 5N illustrates the results of processing the input events shown inFIG. 5M by the component gesture recognizers in pinch gesture recognizer530. In the example shown in FIG. 5N, the first input event is a spatialevent that describes the first touch input, which is a newly-receivedtouch input (e.g., the first input event has a phase value of “touchbegin”). First drag component 532 has identified and stored the initiallocation 540 (“p_(1i)”) of the first touch input. In addition, firstdrag component 532 monitors the amount of movement of the first touchinput across the touch-sensitive surface by determining a distancebetween the current location (“p_(1c)”) of the first touch input and theinitial location (“p_(1i)”) of the first touch input. At initialdetection of the first touch input, when the current location (“p_(1c)”)is equal to the initial location (“p_(1i)”), the touch input has not yetmoved across the touch-sensitive surface, so the amount of movement(“|p_(1c)−p_(1i)|”) is zero. Because the amount of movement is less thanthe minimum threshold amount (“D_(min,th)”), first drag component 532 isin the “possible” state to indicate that drag behavior (e.g., includingmovement of the input) may occur but has not yet been detected. In someembodiments, the “possible” state is an available state for a gesturerecognition component that requires a minimum threshold amount ofmovement of the touch input. Such a component remains in the “possible”state while an input continues to be detected and before the detectedinput has moved by the minimum threshold amount (e.g., for subsequentinput events having phase values of “touch stationary”), and transitionsto the “active” state when the detected input has moved by the minimumthreshold amount (subject to other requirements of the component, ifany, also being satisfied).

First drag component 532 conveys, to parallel combiner 536, the current“possible” state of first drag component 532 and a plurality of valuesidentified from (or determined based on information in) the first inputevent, including an initial timestamp of the first touch input(“t_(1i)”), an instantaneous velocity of the first touch input(“v_(1i)”), an initial location of the first touch input (“p_(1i)”), anda current location of the first touch input (“p_(1i)” at initialdetection of the first touch input).

Similarly, the second input event is also a spatial event that describesan ongoing touch input. Second drag component has identified and storedthe initial location 542 (“p_(2i)”) of the second touch input. Becausethe amount of movement of the second touch input (“|p_(2c)−p_(2i)|”) isless than the minimum threshold amount (“D_(min,th)”), second dragcomponent 534 is in the “possible” state. Second drag component 534conveys, to parallel combiner 536, the current “possible” state ofsecond drag component 532 and a plurality of values identified from (ordetermined based on information in) the second input event, including aninitial timestamp of the second touch input (“t_(2i)”), an instantaneousvelocity of the second touch input (“v_(2i)”), an initial location ofthe second touch input (“p_(2i)”), and a current location of the secondtouch input (“p_(2i)” at initial detection of the second touch input).

Parallel combiner 536 receives the “possible” states and values fromfirst drag component 532 and second drag component 534. Because bothdrag components are in the “possible” state, parallel combiner 536 isalso in the “possible” state. Parallel combiner 536 conveys its current“possible” state and all of the values received from first dragcomponent 532 and second drag component 534 to pinch component 538. Insome embodiments, parallel combiner 536 receives from each dragcomponent an array of the values from that drag component. In someembodiments, parallel combiner 536 combines the received arrays into alarger array that includes all of the values received from the dragcomponents.

Pinch component 538 receives the “possible” state and values fromparallel combiner 536. Because parallel combiner 536 is in the“possible” state, pinch component 538 is also in the “possible” state.Pinch component 538 determines and conveys a scale value, and optionallya scale velocity, based on the values received from parallel combiner536 (e.g., based on the locations of each touch input relative to theirinitial positions). Because pinch component 538 is the root node ofpinch gesture recognizer 530, the overall state of pinch gesturerecognizer 530 is the “possible” state, and the overall output values ofpinch gesture recognizer 530 are those of pinch component 538.

FIG. 5O illustrates an example of successful recognition of a pinchgesture. In particular, FIG. 5O illustrates the results of processing asecond pair of input events that are received after the first and secondinput events described with respect to FIGS. 5M-5N. The second pair ofinput events include a third input event that is associated with thefirst touch input being maintained on and moved across thetouch-sensitive surface by at least the minimum threshold distance and afourth input event that is associated with the second touch input beingmaintained on and moved across the touch-sensitive surface by at leastthe minimum threshold distance. In the example illustrated in FIG. 5O,the third and fourth input events are spatial events with phase valuesof “touch movement.” First drag component 532 has identified the thirdinput event as a spatial event for the ongoing first touch input (asindicated by the “touch movement” phase value) and has determined thatthe amount of movement of the first touch input (“p_(1c)−p_(1i)”) isgreater than the minimum threshold amount (“D_(min,th)”). Accordingly,first drag component 532 has transitioned to the “active” state. Firstdrag component 532 conveys, to parallel combiner 536, the current“active” state of first drag component 532 and values identified from(or determined based on information in) the third input event, includinga current timestamp of the first touch input (“t_(1c)”), a currentinstantaneous velocity of the first touch input (“v_(1c)”), the initiallocation of the first touch input (“p_(1i)”), and a current location ofthe first touch input (“p_(1c)”).

Similarly, second drag component 534 has identified the fourth inputevent as a spatial event for the ongoing second touch input (asindicated by the “touch movement” phase value) and has determined thatthe amount of movement of the second touch input (“p_(2c)−p_(2i)”) isgreater than the minimum threshold amount (“D_(min,th)”). Accordingly,second drag component 534 has transitioned to the “active” state. Seconddrag component 534 conveys, to parallel combiner 536, the current“active” state of second drag component 534 and values identified from(or determined based on information in) the fourth input event,including a current timestamp of the second touch input (“t_(2c)”), acurrent instantaneous velocity of the second touch input (“v_(2c)”), theinitial location of the second touch input (“p_(2i)”), and a currentlocation of the second touch input (“p_(2c)”).

Because both drag components have transitioned to the “active” state,parallel combiner 536 has also transitioned to the “active” state. Insome embodiments, a pinch gesture can be performed by moving only onetouch input while the other touch input remains stationary. Accordingly,in some embodiments, parallel combiner 536 transitions to the “active”state in response to at least one of its child drag componentstransitioning to the “active” state (e.g., even while the other childdrag component remains in the “possible” state). In FIG. 5O, parallelcombiner 536 conveys its current “active” state and all of the valuesreceived from first drag component 532 and second drag component 534 topinch component 538.

Because parallel combiner 536 is in the “active” state, pinch component538 is also in the “active” state. Pinch component 538 determines andconveys a (current) scale value, and optionally a (current) scalevelocity, based on the values received from parallel combiner 536 (e.g.,based on the current locations of each touch input relative to theirinitial positions). Accordingly, the overall state of pinch gesturerecognizer 530 is the “active” state, and the overall output values ofpinch gesture recognizer 530 are those of pinch component 538.

FIG. 5P illustrates an example of continued successful recognition ofthe pinch gesture recognized in FIG. 5O. In particular, FIG. 5Pillustrates the results of processing a third pair of input events thatare received after the second pair of input events described withrespect to FIG. 5O. The third pair of input events include a spatialevent that is associated with the first touch input being maintained onthe touch-sensitive surface at a location that is least the minimumthreshold distance from its initial location and a spatial event that isassociated with liftoff of the second touch input from thetouch-sensitive surface (e.g., having a phase value of “touch end”).Accordingly, first drag component 532 remains in the “active” andconveys, to parallel combiner 536, the current “active” state and theassociated values as described with respect to FIG. 5O.

Second drag component 534 has identified the spatial event as beingassociated with a completed touch input (as indicated by the “touch end”phase value”) and accordingly has transitioned to the “ended” state.Second drag component 534 conveys its current “ended” state and theassociated values identified from (or determined based on informationin) the “touch ended” input event, including an ending timestamp of thesecond touch input (“t_(2e)”), an instantaneous velocity of the secondtouch input at the time of liftoff (“v_(2e)”), the initial location ofthe second touch input (“p_(2i)”), and the ending location of the secondtouch input at the time of liftoff (“p_(2e)”).

In some embodiments, the pinch gesture recognizer remains in the“active” state as long as one touch input remains “active” even if theother touch input has “ended.” That is, a pinch gesture recognizer thatis “active” while a user performs a pinch gesture using two fingers incontact with a touch-sensitive surface remains “active” even after theuser lifts one finger from the touch-sensitive surface as long as theother finger is maintained on the touch-sensitive surface. The user mayplace the lifted finger back down on the touch-sensitive surface toresume the pinch gesture. Accordingly, although second drag component534 has transitioned to the “ended” state in FIG. 5P, parallel combiner536 remains in the “active” state. Parallel combiner 536 conveys itscurrent “active” state and all of the values received from first dragcomponent 532 and second drag component 534 to pinch component 538.

Because parallel combiner 536 remains in the “active” state, pinchcomponent 538 also remains in the “active” state, and determines andconveys a (current) scale value, and optionally a (current) scalevelocity, based on the values received from parallel combiner 536.Accordingly, the overall state of pinch gesture recognizer 530 remainsin the “active” state, and the overall output values of pinch gesturerecognizer 530 are those of pinch component 538.

FIG. 5Q illustrates an example of completion of the pinch gesturerecognized in FIGS. 5O-5P. In particular, FIG. 5Q illustrates theresults of processing an additional input event that is received afterthe third pair of input events described with respect to FIG. 5 and thatis associated with liftoff of the first touch input from thetouch-sensitive surface (e.g., having a phase value of “touch end”).Accordingly, first drag component 534 has transitioned to the “ended”state. First drag component 534 conveys its current “ended” state andthe associated values identified from (or determined based oninformation in) the “touch ended” input event, including an endingtimestamp of the first touch input (“t_(1e)”), an instantaneous velocityof the first touch input at the time of liftoff (“v_(1e)”), the initiallocation of the first touch input (“p_(1i)”), and the ending location ofthe first touch input at the time of liftoff (“p_(1e)”).

Because both drag components have transitioned to the “ended” state,parallel combiner 536 has also transitioned to the “ended” state.Parallel combiner 536 conveys its current “ended” state and all of thevalues received from first drag component 532 and second drag component534 to pinch component 538. Accordingly, the overall state of pinchgesture recognizer 530 is the “ended” state, indicating that a pinchgesture has been recognized and has ended, and the overall output valuesof pinch gesture recognizer 530 are those of pinch component 538. Thescale velocity is optionally used to continue to adjust the scale of theuser interface or user interface element to which the pinch gesture wasdirected even after the pinch gesture has ended.

In some embodiments, a respective view of a user interface includes arotation gesture recognizer having the same component gesturerecognizers as the pinch gesture recognizer 530 described above, exceptthat the pinch component 538 is replaced with a rotation component (notshown). Furthermore, operation of the rotation gesture recognizer andits component recognizers are the same as that described above for pinchgesture recognizer 530, except that the rotation component determines anangle, or rotation amount, and optionally an angular or rotationvelocity, in accordance with the position values and optionally thevelocity values received from the parallel component 536, when at leastone of the drag components 532 of the rotation gesture recognizer is inthe active state.

FIG. 6A-6C illustrate examples of gesture recognition hierarchiesgenerated from a view hierarchy of views in a user interface based onreceived inputs.

FIG. 6A shows device 100 displaying user interface 600. User interface600 includes a plurality of views 602 (labeled “View A”), 606 (labeled“View B”), 612 (labeled “View C”), and 616 (labeled “View D”). View 602is the highest view in view hierarchy 630 and includes long pressgesture recognizer 604. View 606 is a child view of view 602 in viewhierarchy 630 and includes scroll gesture recognizer 608 and pinchgesture recognizer 610 (e.g., similar to pinch gesture recognizer 530,FIG. 5M). View 612 is a first child view of view 606 in view hierarchy630 and includes a first tap gesture recognizer 614 (e.g., similar totap gesture recognizer 500, FIG. 5A). View 616 is a second child view ofview 606 in view hierarchy 630 and includes a second tap gesturerecognizer 618 (e.g., similar to tap gesture recognizer 500, FIG. 5A).In some embodiments, second tap gesture recognizer 618 includesinstances of the same component gesture recognizers are and first tapgesture recognizer 614, and thus those component gesture recognizers arereused two or more times in concurrently instantiated gesturerecognizers. More generally, in some embodiments, two or more instancesof a respective (or first) component gesture recognizer are included inconcurrently instantiated gesture recognizers; and in some embodiments,two or more instances of each of a plurality of component gesturerecognizers are included in concurrently instantiated gesturerecognizers (e.g., in the gesture recognition hierarchy, discussedbelow, for a respective user interface 600).

FIG. 6A further illustrates a touch input 620 received at device 100.Device 100 (e.g., using hit view determination module 172) determinesthat view 612 is the hit view for touch input 620 (e.g., view 612 is thelowest view in view hierarchy 630 in which touch input 620 has occurred,and thus should receive priority for handling input events associatedwith touch input 620). Accordingly, view 612 is highlighted in viewhierarchy 630. In some embodiments, the gesture recognizers 604, 608,610, 614, and 618 are created (e.g., instantiated) and executed ondevice 100 without regard to whether a user input has been received. Insome embodiments, one or more of the gesture recognizers 604, 608, 610,614, and 618 are created and executed on the device in response to thedevice receiving a user input (e.g., touch input 620).

In response to receiving touch input 620, device 100 generates gesturerecognition hierarchy 640 based on view hierarchy 630. In someembodiments, as shown in FIG. 6A, the generated gesture recognitionhierarchy includes only the gesture recognizers of views that correspondto the location of the touch input (e.g., the hit view and all of itspredecessors in view hierarchy). Accordingly, gesture recognitionhierarchy 640 includes only the gesture recognizers of hit view 612,parent view 606 of view 612, and grandparent view 602 of view612—namely, first tap gesture recognizer 614 of hit view 612, scrollgesture recognizer 608 and pinch gesture recognizer 610 of view 606, andlong press gesture recognizer 604 of view 602. In some embodiments, thegenerated gesture recognition hierarchy includes gesture recognizers forall views in the view hierarchy (e.g., such a gesture recognitionhierarchy would also include second tap gesture recognizer 618 of view616, which does not correspond to the location of touch input 620).

In addition, because view 612 has been determined to be the hit view,the gesture recognizer(s) of hit view 612 have the highest priority forprocessing touch input 620, over the gesture recognizers of other viewsin the view hierarchy. Accordingly, gesture recognition hierarchy 640assigns the highest priority to first tap gesture recognizer 614 usingexclusive combiner 642. An exclusive combiner defines a relationshipbetween multiple child (component) gesture recognizers by requiring thatthe left-hand-side child fail in order for the right-hand-side child tosucceed. For exclusive combiners with more than two children, arespective child is allowed to succeed only when every child to its lefthas failed. Thus, because all of the gesture recognizers in gesturerecognition hierarchy 640 other than tap gesture recognizer 614 are onthe right-hand-side of exclusive combiner 542, gesture recognitionhierarchy requires that first tap gesture recognizer 614 fail in orderfor any other gesture recognizer in hierarchy 640 to succeed. It isnoted that the terms “right” and “left” in this discussion are distinctbut interchangeable, and similarly the terms “right-hand” and“left-hand” in the present discussion are distinct but interchangeable.More generally, in some embodiments, each distinct input position of theexclusive combiner 642 or 644 is assigned a respective priority, and thechild connected to a particular input of the exclusive combiner 642 or644 is allowed to succeed only when all the children connected to lowerpriority inputs of the exclusive combiner 642 or 644 have failed.

Because view 606 is the parent of the hit view (e.g., the second-lowestview in view hierarchy 630 that corresponds to touch input 620), thegesture recognizers of view 606 have the second-highest priority forprocessing touch input 620. Accordingly, the two gesture recognizers ofview 606 (e.g., scroll gesture recognizer 608 and pinch gesturerecognizer 610) both have priority, defined by exclusive combiner 644,over other gesture recognizers in gesture recognition hierarchy 640(e.g., long press gesture recognizer 604). In some embodiments, when asingle view includes multiple gesture recognizers, a combiner is used todefine a priority or other relationship between the multiple gesturerecognizers. In the example shown in FIG. 6A, simultaneous combiner 646is used to define a relationship between scroll gesture recognizer 608and pinch gesture recognizer 610 of view 606 such that scroll gesturerecognizer 608 and pinch gesture recognizer 610 are allowed to succeedsimultaneously.

FIG. 6B is similar to FIG. 6A, except that FIG. 6B illustrates a touchinput 622 received at device 100 such that view 616 is determined to bethe hit view (instead of view 612 as in FIG. 6A). Accordingly, view 616is highlighted in view hierarchy 630. In response to receiving touchinput 622, device 100 generates gesture recognition hierarchy 650 basedon view hierarchy 630. Gesture recognition hierarchy 650 includes thegesture recognizers of hit view 616, parent view 606 of view 616, andgrandparent view 602 of view 616—namely, second tap gesture recognizer618 of hit view 616 (instead of first tap gesture recognizer 614 of view612), scroll gesture recognizer 608 and pinch gesture recognizer 610 ofview 606, and long press gesture recognizer 604 of view 602. Becauseview 616 has been determined to be the hit view, second tap gesturerecognizer 618 has the highest priority for processing touch input 622over the gesture recognizers of other views in the view hierarchy.Accordingly, gesture recognition hierarchy 650 is similar to gesturerecognition hierarchy 640 (Figure A), except that second tap gesturerecognizer 618 of view 616 replaces first tap gesture recognizer 614 ofview 612.

FIG. 6C is similar to FIG. 6A, except that FIG. 6C illustrates atwo-contact touch input 624 received at device 100. In some embodiments,the hit view for a multiple-contact touch input is determined based on acentroid of the multiple contacts. In the example shown in FIG. 6C, thehit view determined for touch input 624 is view 606 (the viewcorresponding to a location that is approximately halfway between thetwo contacts of touch input 624). Accordingly, view 606 is highlightedin view hierarchy 630. In response to receiving touch input 624, device100 generates gesture recognition hierarchy 660. Because view 606 hasbeen determined to be the hit view, scroll gesture recognizer 608 andpinch gesture recognizer 610 of view 606, which are allowed bysimultaneous combiner 664 to succeed simultaneously, both have thehighest priority for processing touch input 624 over the gesturerecognizers of other views in the view hierarchy (e.g., long pressgesture recognizer 604). Accordingly, simultaneous combiner is on theleft-hand-side of exclusive combiner 662, while long press gesturerecognizer 604 is on the right-hand-side. In other words, gesturerecognition hierarchy 660 is similar to gesture recognition hierarchy640 (Figure A), except that first tap gesture recognizer 614 and itsassociated exclusive combiner 642 are omitted.

In some embodiments, the hit view for touch input 624 is determined tobe view 612, because at least one contact of touch input 624 correspondsto view 612, and because view 612 is lower than view 606. In some suchembodiments, gesture recognition hierarchy 660 also includes first tapgesture recognizer 614 (e.g., the gesture recognition hierarchy is thesame as gesture recognition hierarchy 640, FIG. 6A).

FIGS. 7A-7E are flow diagrams illustrating method 700 of processinginputs using gesture recognizers assembled from component gesturerecognizers in accordance with some embodiments. Method 700 is performedat an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with an input device (e.g., touchscreen 112, FIG. 1A, touchpad 355 or keyboard/mouse 350, FIG. 3),optionally a display (e.g., touch screen 112, FIG. 1A, or display 340,FIG. 3), and optionally one or more sensors to detect intensity ofcontacts with an input device that includes a touch-sensitive surface(e.g., contact intensity sensor(s) 165, FIG. 1A). In some embodiments,the display is a touch-screen display with a touch-sensitive surface onor integrated with the display. In some embodiments, the display isseparate from the touch-sensitive surface. Some operations in method 700are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, method 700 provides an intuitive way for anelectronic device to process a detected input using a modular approachthat divides a larger set of input event handling requirements intosmaller subsets of event handling requirements associated with andprocessed using component gesture recognizers that make up a gesturerecognizer, such that the smaller subsets of event handling requirementscan be more quickly processed than the larger set. This modular approachincreases the number, extent, and complexity of gestures that canpotentially be recognized. Reusing (instances of) modules acrossmultiple gesture recognizers provides consistency in gesture recognitioncapabilities. In addition, in contrast to an approach that processesinputs using monolithic gesture recognizers (i.e., gesture recognizersthat are not modular), this modular approach provides design flexibilityin that modules can be added to or removed from a gesture recognizer, orindividual modules in a gesture recognizer can be substituted withmodified versions, without requiring an entirely new monolithic gesturerecognizer to be designed. The modular approach also reduces thecomputational load imposed on an electronic device by touch and otherinputs and gestures, which in turn improves device responsiveness andreduces latency. Reducing latency in responding to inputs also reducesuser mistakes when operating/interacting with the device, such asduplicative or extraneous inputs made by the user while waiting for thedevice to respond to the user's earlier input(s). Reducing the numberand/or extent of the inputs from a user enhances the operability of thedevice and makes the user-device interface more efficient, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

The device detects (702) an input via the input device (e.g., a touchinput on the touch-sensitive surface, a mouse input using one or morebuttons of a mouse, etc.).

In response to detecting the input, the device monitors (704) the inputusing a gesture recognizer. The gesture recognizer includes (706) aplurality of component gesture recognizers that define requirements forrecognition of a gesture (e.g., the gesture recognizer is an assembledgesture recognizer, assembled using the plurality of component gesturerecognizers from a set of available component gesture recognizers). Afirst component gesture recognizer from the plurality of componentgesture recognizers defines a first requirement for recognition of thegesture (e.g., a requirement with respect to location, contactintensity, minimum duration, maximum duration, distance (optionally witha minimum and/or maximum distance requirement), etc.), and a secondcomponent gesture recognizer from the plurality of component gesturerecognizers defines a second requirement for recognition of the gesture(e.g., a requirement with respect to location, contact intensity,minimum duration, maximum duration, distance (optionally with a minimumand/or maximum distance requirement), etc.). In some embodiments, thegesture recognizer is formed (e.g., created or instantiated) in responseto the input being detected. In some embodiments, the gesture recognizeris associated with a view in a plurality of views of a softwareapplication executing on the electronic device, and the gesturerecognizer is formed in accordance with a determination that thelocation of the detected input corresponds to the view with which thegesture recognizer is associated. In some embodiments, the gesturerecognizer corresponds specifically to the aforementioned view, orcomprises a component of the application that responds to touch inputsin the aforementioned view. Example gesture recognizers that have beenassembled from a plurality of component gesture recognizers are shown inand described herein with respect to FIGS. 5A-5Q.

In accordance with a determination that the input satisfies firstgesture recognition criteria that include the first requirement of thefirst component gesture recognizer and the second requirement of thesecond component gesture recognizer, the device recognizes (708) a firstgesture using the gesture recognizer. In some embodiments, the set ofavailable component gesture recognizers include component gesturerecognizers that identify input events (e.g., touch events, mouseevents, etc.) having particular properties (e.g., input events thatinclude location information and/or translation (movement) information).Examples of component gesture recognizers that identify input eventsinclude a spatial event listener (such as spatial event listener 502,FIG. 5A), a pan event listener, and a drag event listener (such as dragevent listeners 532 and 534, FIG. 5M), etc.).

In some embodiments, the set of available component gesture recognizersinclude component gesture recognizers for determining whether particularproperties of an input (e.g., current location, current timestamp,current intensity, etc., optionally in conjunction with one or morepreviously-determined properties such as starting location, startingtimestamp, etc.) satisfy particular requirements for recognition of agesture (e.g., a distance requirement (see discussion of distancecomponent 506, FIG. 5A), a (timing) duration requirement (see discussionof max duration component 504, FIG. 5A), or an intensity thresholdrequirement, etc.). In some embodiments, the set of available componentgesture recognizers include wrappers that include one or more othercomponent gesture recognizers and whose outputs depend on the results ofthe included component gesture recognizer (e.g., a repeating componentgesture recognizer (such as repeater 522, FIG. 5G), as described in moredetail herein) and/or on the results of other gesture recognizers orcomponent gesture recognizers having a higher priority than the includedcomponent gesture recognizer (e.g., a pausing component gesturerecognizer (such as pause-for-predecessor 508, FIG. 5A), as described inmore detail herein).

In some embodiments, the set of available component gesture recognizersinclude combiners, where a respective combiner combines results(sometimes called component gesture recognizer outputs or recognitionresults, or inputs to the combiner) generated by two or more componentgesture recognizers and defines a requirement for recognition of agesture based on relationship between the component gesture recognizerswhose results are combined using the combiner (e.g., a gating componentgesture recognizer (such as gating combiners 510 and 512, FIG. 5A), asimultaneous component gesture recognizer (such as simultaneous combiner646, FIG. 6A), an exclusive component gesture recognizer (such asexclusive combiners 642 and 644, FIG. 6A), a sequential componentgesture recognizer, or a parallel component gesture recognizer (such asparallel combiner 536, FIG. 5M), etc., as described in more detailherein).

In some embodiments, determining whether the input satisfies the firstgesture recognition criteria includes: determining, using the firstcomponent gesture recognizer, whether the input satisfies the firstrequirement defined by the first component gesture recognizer;determining, using the second component gesture recognizer, whether theinput satisfies the second requirement defined by the first componentgesture recognizer; and determining whether the input satisfies thefirst gesture recognition criteria based on the respectivedeterminations made using the first component gesture recognizer and thesecond component gesture recognizer.

In some embodiments, the first component gesture recognizer has (710) acurrent state of a plurality of available states (e.g., determined basedon whether the input satisfies the first requirement of the firstcomponent gesture recognizer); and the second component gesturerecognizer has a current state of the plurality of available states(e.g., determined based on whether the input satisfies the secondrequirement of the second component gesture recognizer). In someembodiments, available states for a respective component gesturerecognizer include “possible,” “active,” “ended,” and “failed.” Examplesof the transitions of a component gesture recognizer between theavailable states are shown in and described herein with respect to FIGS.5A-5Q. Having separate states for different component gesturerecognizers comports with modular design of gesture recognizers, whichsimplifies event handling and reduces the computational load on thedevice when processing inputs. This improves device responsiveness andreduces latency, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the device determines (712) a current state (e.g.,of the plurality of available states (e.g., “possible,” “active,”“ended,” and “failed”)) of the gesture recognizer based on the currentstate of the first component gesture recognizer and the current state ofthe second component gesture recognizer. In some embodiments, theoverall state of the gesture recognizer is determined based on combinerrules. In one example, a gesture recognizer includes a first componentgesture recognizer and a second component gesture recognizer that areassociated using a gating component gesture recognizer (also called agating combiner). In this example, the gating combiner is in a Failedstate when the second component gesture recognizer is in a Failed state;and, when the second component gesture recognizer is not in a Failedstate, the gating combiner passes through the state of the firstcomponent gesture recognizer (e.g., the gating combiner operatessimilarly to a logical AND gate). As described herein with reference toFIGS. 5A-5F, the current overall state of tap gesture recognizer 500 isdetermined based on the current state of gating combiner 512 (whosestate is in turn determined based on other component gesture recognizers502, 504, 506, 508, and 510 in tap gesture recognizer 500). In anotherexample, as described herein with reference to FIG. 5G, the currentoverall state of double-tap gesture recognizer 520 is determined basedon the current states of its component gesture recognizers 522 and 524.Determining an overall state of the gesture recognizer based on statesof the component gesture recognizers comports with modular design ofgesture recognizers, which simplifies event handling and reduces thecomputational load on the device when processing inputs. This improvesdevice responsiveness and reduces latency, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome andby reducing user mistakes when operating/interacting with the device).

In some embodiments, monitoring the input using the gesture recognizerincludes (714): receiving, at the gesture recognizer, first informationthat describes the input at a first point in time (e.g., a touch eventcorresponding to the first point in time); processing the firstinformation using the first component gesture recognizer to determine acurrent state of the first component gesture recognizer, of theplurality of available states, for the first point in time; andprocessing the first information using the second component gesturerecognizer to determine a current state of the second component gesturerecognizer, of the plurality of available states, for the first point intime, as described herein with reference to the results of processing ofthe first input event as illustrated in FIG. 5C. In some embodiments,monitoring the input using the gesture recognizer also includesreceiving, at the gesture recognizer, second information that describesa change in the input at a second point in time later than the firstpoint in time. In some embodiments, the gesture recognizer receives andprocesses the second information for the second point in time after thegesture recognizer has received and processed the first information. Insome embodiments, monitoring the input using the gesture recognizerfurther includes: processing the second information using the firstcomponent gesture recognizer to determine a current state of the firstcomponent gesture recognizer, of the plurality of available states, forthe second point in time (e.g., to update the state of the firstcomponent gesture recognizer from a previous state, such as its statefor the first point in time); and processing the second informationusing the second component gesture recognizer to determine a currentstate of the second component gesture recognizer, of the plurality ofavailable states, for the second point in time (e.g., to update thestate of the second component gesture recognizer from a previous state,such as its state for the first point in time), as described herein withreference to the results of processing of the second, third, or fourthinput events as illustrated in FIGS. 5D-5F, respectively. Monitoring aninput over time using separate component gesture recognizers with statesthat evolve over time comports with modular design of gesturerecognizers, which simplifies event handling and reduces thecomputational load on the device when processing inputs. This improvesdevice responsiveness and reduces latency, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome andby reducing user mistakes when operating/interacting with the device).

In some embodiments, one or more component gesture recognizers in thegesture recognizer include (716) one or more parameters (e.g., a pointvalue that describes a location of the input, or a timestamp thatdescribes a time associated with the input) that describe the input(e.g., initial location 516, or initial time 514, FIG. 5C). In someembodiments, monitoring the input using the gesture recognizer includesdetermining values of the one or more parameters using the one or morecomponent gesture recognizers in the gesture recognizer. In someembodiments, the first gesture recognition criteria include arequirement that a respective parameter meet a respective threshold inorder for the first gesture to be recognized. For example, the firstgesture recognition criteria include a requirement (defined by arespective component gesture recognizer) that a distance traveled by theinput (e.g., an amount of movement of a touch input across atouch-sensitive surface) meet a respective distance threshold (e.g., theinput must move at least a first threshold amount, the input must notmove more than a second threshold amount, or the input must move atleast the first threshold amount but not more than the second thresholdamount).

In some embodiments, the gesture recognizer generates/sends events to asoftware application in accordance with changes in the one or moreparameters. In some embodiments, the gesture recognizer generates/sendsone or more events to the software application prior to determiningwhether the input satisfies the first gesture recognition criteria. Insome embodiments, a respective event of the one or more events includesa phase value corresponding to a current state of the gesture recognizer(e.g., “possible,” “active,” “ended,” or “failed”). Using componentgesture recognizers in a gesture recognizer to determine values ofparameters that describe the input provides the gesture recognizer withinformation about the input that is needed for processing inputs, whichsimplifies event handling and reduces the computational load on thedevice when processing inputs. This improves device responsiveness andreduces latency, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the gesture recognizer is (718) a gesturerecognition tree (e.g., a tree data structure) having a plurality ofnodes, and each node of the gesture recognition tree includes arespective component gesture recognizer (e.g., as described herein withreference to FIGS. 5A-5Q). In some embodiments, monitoring the inputusing the gesture recognizer includes conveying information thatdescribes the input at a respective point in time from component gesturerecognizers at respective nodes having child nodes in the gesturerecognition tree to component gesture recognizers at the child nodes inthe gesture recognition tree (e.g., as described herein with referenceto FIGS. 5B, 5G, 5J, and 5M). In some embodiments, a (parent) componentgesture recognizer having multiple child nodes (e.g., a combiner)conveys information that describes the input (e.g., input events) to itschild component gesture recognizers based on properties of the (parent)component gesture recognizer. Some combiners, such as simultaneouscombiners and exclusive combiners, convey information about an input(e.g., input events) to all of their child component gesture recognizers(e.g., as described herein with reference to simultaneous combiner 646and exclusive combiners 642 and 644, FIG. 6A). In some embodiments, acombiner (e.g., an exclusive combiner) sends a particular input event toall child component gesture recognizers of the combiner by sending theparticular input event to one child at a time for processing of theinput event by each child in turn.

Some combiners, such as sequential combiners and parallel combiners,convey information about an input to only a subset of their childcomponent gesture recognizers. For example, a sequential combinerconveys respective information about an input (e.g., a respective inputevent) to (only) one respective child component gesture recognizer.While a respective input is detected, a sequential combiner first sendsinput events about the respective input to its first child. After thefirst child succeeds, the sequential combiner sends subsequent inputevents to its second child, and so on for each additional child. If anychild fails, the sequential combiner fails. In another example, parallelcombiners associate one or more of their child component gesturerecognizers with one or more respective inputs and convey informationabout a respective input only to the associated child gesturerecognizer. Where multiple touches are detected on a touch-sensitivesurface, a first child gesture recognizer of a parallel combiner isassociated with a first touch of the multiple touches, a second childgesture recognizer of the parallel combiner is associated with a secondtouch of the multiple touches, and so on for each touch of the multipletouches. In this example, input events describing the first touch aresent by the parallel combiner to the first child gesture recognizer (andnot to the second or any other child gesture recognizers); similarly,input events describing the second touch are sent by the parallelcombiner to the second child gesture recognizer (and not to the first orany other child gesture recognizers). An example of parallel combinerbehavior is described herein with reference to parallel combiner 536,FIGS. 5M-5Q.

In some embodiments, monitoring the input using the gesture recognizeralso includes determining states of component gesture recognizers atrespective nodes in the gesture recognition tree based on theinformation that describes the input at the respective point in timeand, in accordance with a determination that a respective node has oneor more child nodes, based on respective states of respective componentgesture recognizers at the one or more child nodes determined based onthe information that describes the input at the respective point intime. In some embodiments, the state of a respective component gesturerecognizer is further based on respective values determined using therespective component gesture recognizers at the one or more child nodes.That is, the state of a respective component gesture recognizer isdetermined based on one or more of: the information about the input(e.g., an input event), determined states (based on the informationabout the input) of its child component gesture recognizers, if any,and/or determined values of its child component gesture recognizers, ifany.

Arranging component gesture recognizers in a tree structure enables anorganized and orderly flow for input events to be processed, by definingrelationships between the component gesture recognizers including, forexample, setting priorities between component gesture recognizers, whichsimplifies input event handling and reduces the computational load onthe device when processing inputs. This improves device responsivenessand reduces latency, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, monitoring the input using the gesture recognizerfurther includes (720) conveying the determined states of the componentgesture recognizers at child nodes in the gesture recognition tree tocomponent gesture recognizers at parent nodes of the child nodes in thegesture recognition tree. In some embodiments, determining whether theinput satisfies the first gesture recognition criteria for recognizingthe first gesture includes determining a state of the gesturerecognition tree based on the determined states of the component gesturerecognizers in the gesture recognition tree (e.g., as described hereinwith reference to FIGS. 5C-5F, 5H-5I, 5K-5L, and 5N-5Q). Determiningstates of parent component gesture recognizers based on states of childcomponent gesture recognizers enables more complex input processingwithout increasing the amount of processing required at the parentcomponent gesture recognizer. Dividing a larger set of processingrequirements into smaller subsets of processing requirements simplifiesevent handling and reduces the computational load on the device whenprocessing inputs. This improves device responsiveness and reduceslatency, thereby enhancing the operability of the device and making theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, monitoring the input using the gesture recognizerincludes (722) determining values of one or more component gesturerecognizers at respective nodes in the gesture recognition tree based onthe information that describes the input at the respective point intime. In some embodiments, the values are determined based on statesand/or values of child component gesture recognizers. In someembodiments, determining a state of a respective component gesturerecognizer at a respective node is further based on a determined valueof a component gesture recognizer at a child node of the respectivenode, in accordance with a determination that the component gesturerecognizer at the child node has a determined value.

For example, a component gesture recognizer that defines a thresholdrequirement for a parameter has a child component gesture recognizerthat determines a value of the parameter, and the (parent) componentgesture recognizer determines its state based on whether the determinedvalue from the child component gesture recognizer satisfies thethreshold requirement. In some embodiments, the (parent) componentgesture recognizer also determines a value of a parameter, and in suchcases the component gesture recognizer determines its value based on adetermined value of its child component gesture recognizer (or based onrespective values of two or more child component gesture recognizers).In another example, a component gesture recognizer (e.g., pinchcomponent 538, FIG. 5N) determines a scale value based on a firstlocation value received (directly or indirectly) from a first childcomponent gesture recognizer (e.g., first drag component 532, FIG. 5N)and a second location value received from a second child componentgesture recognizer (e.g., second drag component 534, FIG. 5N). In someembodiments, the first child component gesture recognizer is a root nodeof a first pan gesture recognizer, and the second child componentgesture recognizer is a root node of a second pan gesture recognizer.

Determining states of parent component gesture recognizers based oninformation about the input (e.g., values of parameters that describethe input) determined by child component gesture recognizers enablesmore complex input processing without increasing the amount ofprocessing required at the parent component gesture recognizer. Dividinga larger set of processing requirements into smaller subsets ofprocessing requirements simplifies event handling and reduces thecomputational load on the device when processing inputs. This improvesdevice responsiveness and reduces latency, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome andby reducing user mistakes when operating/interacting with the device).

In some embodiments, the plurality of component gesture recognizers inthe gesture recognizer are (724) selected from a plurality of availablecomponent gesture recognizers that include: combiners that combineinformation from two or more component gesture recognizers and definerequirements for recognition of a gesture based on relationships betweenthe component gesture recognizers combined using the combiners; andinput parameter recognizers that determine values of parameters thatdescribe the input (e.g., location, timestamp, intensity) and/or definethreshold requirements (e.g., lower and/or upper limits) for parametersthat describe the input (e.g., threshold distance traveled by the input,threshold duration of the input, threshold contact intensity of theinput). Using combiners to define and monitor relationships betweencomponent gesture recognizers, and input parameter recognizers tomonitor information about the input (e.g., values of parameters thatdescribe the input) and define threshold requirements for the input,enables more complex input processing while dividing a larger set ofprocessing requirements into smaller subsets of processing requirementsthat can be more quickly processed than the larger set. This improvesdevice responsiveness and reduces latency, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome andby reducing user mistakes when operating/interacting with the device).

In some embodiments, the gesture recognizer is (726) associated with anapplication (e.g., application 136-1, FIG. 1B), and the plurality ofcomponent gesture recognizers in the gesture recognizer are instances(e.g., application-specific instances) of respective component gesturerecognizers in a plurality of available component gesture recognizersprovided by an application-independent module (e.g., anapplication-independent library of component gesture recognizers,provided, for example, by an operating system or an applicationprogramming interface (API) on the device, such asapplication-independent software module 195, FIG. 1B). Providing aframework of available component gesture recognizers such that instancesof the available component gesture recognizers can be used to formgesture recognizers reduces the burden on the device to support andexecute different gesture recognition processes across differentapplications and improves consistency of gesture recognitionfunctionality. This reduces the computational load imposed on thedevice, which in turn improves device responsiveness and reduceslatency, thereby enhancing the operability of the device and making theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the gesture recognizer includes (728) a thirdcomponent gesture recognizer (e.g., a combiner) that defines a thirdrequirement for recognition of a gesture based on a relationship betweenthe first component gesture recognizer and the second component gesturerecognizer (e.g., exclusive, simultaneous, sequential, parallel, orgating combiners). In some embodiments, monitoring the input using thegesture recognizer includes monitoring the state of the first componentgesture recognizer and the state of the second component gesturerecognizer using the third component gesture recognizer to determinewhether the first component gesture recognizer (e.g., the state of thefirst component gesture recognizer) and the second component gesturerecognizer (e.g., the state of the second component gesture recognizer)satisfy the third requirement. In some embodiments, the first gesturerecognition criteria include the third requirement that is based on thepredefined relationship between the first component gesture recognizerand the second component gesture recognizer. Example combiners and theirrequirements/uses are described herein with reference to FIGS. 5A-5Q and6A-6C. Using a third component gesture recognizer to define and monitora relationship between first and second component gesture recognizers,each of which define and monitor a respective subset of event handlingrequirements for recognition of a gesture, increases the complexity ofgestures that can potentially be recognized without increasing thecomputational load on the first and second component gesturerecognizers. This improves device responsiveness and reduces latency,thereby enhancing the operability of the device and making theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the third component gesture recognizer is (730) anexclusive combiner, and the third requirement specifies that the firstcomponent gesture recognizer must fail in order for the second componentgesture recognizer to succeed. In some embodiments, while the firstcomponent gesture recognizer is not in a failed or canceled state, astate of the third component gesture recognizer is based on a state ofthe first component gesture recognizer (e.g., without regard to a stateof the second component gesture recognizer). In some embodiments, whilethe first component gesture recognizer is in a failed or canceled state,a state of the third component gesture recognizer is based on a state ofthe second component gesture recognizer. For example, when the firstcomponent gesture recognizer is in a state other than a failed orcanceled state, the state of the third component gesture recognizer isbased on the state of the first component gesture recognizer, and thethird component gesture recognizer also includes an indication that thestate of the third component gesture recognizer corresponds to the firstcomponent gesture recognizer. In another example, when the firstcomponent gesture recognizer is in a failed or canceled state, the stateof the third component gesture recognizer is based on the state of thesecond component gesture recognizer, and the third component gesturerecognizer also includes an indication that the state of the thirdcomponent gesture recognizer corresponds to the second component gesturerecognizer. Example exclusive combiners are also described herein withreference to FIGS. 6A-6C. Providing an exclusive combiner that requiresits first (child) component gesture recognizer to fail in order for itssecond (child) component gesture recognizer to succeed allows for theassignment of different priorities to different gesture recognizers orcomponent gesture recognizers without increasing the computational loadof the gesture recognizers or component gesture recognizers to which thepriorities are being assigned. This improves the variety of gesturesthat can be recognized while reducing the additional computational loadtypically imposed by monolithic gesture recognizers for increasinglydiverse and complex gestures, which in turn improves deviceresponsiveness and reduces latency, thereby enhancing the operability ofthe device and making the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome and by reducing usermistakes when operating/interacting with the device).

In some embodiments, the third component gesture recognizer is (732) asimultaneous combiner, and the third requirement requires, at arespective point in time, success of at least one of the first componentgesture and the second component gesture recognizer in order for thethird component gesture recognizer to succeed. In some embodiments, thesimultaneous combiner allows both the first component gesture recognizerand the second component gesture recognizer to succeed simultaneously.For example, a simultaneous gesture recognizer that combines a tapgesture recognizer and a double-tap gesture recognizer allows the tapgesture recognizer to succeed when a tap input (e.g., an input having aduration that is less than a predefined threshold duration and an amountof movement that is less than a predefined threshold amount of movement)is recognized, and also allows the double-tap gesture recognizer tosucceed when a second tap input that completes the double-tap gesture isrecognized. Providing a simultaneous combiner that requires success ofat least one (child) gesture recognizer or component gesture recognizeryet allows for multiple (child) gesture recognizers or component gesturerecognizers to succeed improves the ability of the device tosimultaneously recognize and process multiple gestures, and thus providethe user with additional control options, without requiring additionalinputs or cluttering the user interface with additional displayedcontrols. This reduces the additional computation load typically imposedby processing multiple gestures simultaneously using monolithic gesturerecognizers, which improves device responsiveness and reduces latency,and also enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the third component gesture recognizer is a gatingcombiner, and the third requirement requires, at a respective point intime, success of the first component gesture and success of the secondcomponent gesture recognizer in order for the third component gesturerecognizer to succeed. In other words, the gating combiner requiressuccess of both the first component gesture recognizer and the secondcomponent gesture recognizer at least at one point in time (e.g., onecomponent gesture recognizer may succeed before the other, but theremust be at least one moment of overlap where both have succeeded) (e.g.,the gating combiner operates as a logical AND gate). Example gatingcombiners are also described herein with reference to FIGS. 5A-5F.

In some embodiments, a respective component gesture recognizer is deemedto succeed when its respective requirement for gesture recognition issatisfied. For example, as discussed above with respect to FIGS. 5A-5F,a tap gesture recognizer requires that (a) a distance traveled by aninput (e.g., an amount of movement of the input across a touch-sensitivesurface) satisfy (e.g., be within) a predefined threshold distance and(b) a duration of the input (e.g., an amount of time during which theinput is detected anywhere on the touch-sensitive surface) satisfy(e.g., be less than) a predefined threshold duration. In the tap gesturerecognizer example, a gating combiner (e.g., gating combiner 512) isused to require that both requirements (a) and (b) are met in order fora tap gesture to be recognized. Stated another way, if the secondcomponent gesture recognizer (e.g., distance component recognizer 506)fails, the gating combiner (e.g., gating combiner 51) fails, and if thesecond component gesture recognizer has not failed, the gating combinerpasses through as its output the state and any values output by thefirst component gesture recognizer (e.g., gating combiner 510).

In some embodiments, the third component gesture recognizer is aparallel combiner that requires, at a respective point in time, successof the first component gesture recognizer and success of the secondcomponent gesture. In one example, a parallel combiner is used in apinch gesture recognizer to define a relationship between a firstcomponent gesture recognizer that is a first drag component gesturerecognizer, and a second component gesture recognizer that is a seconddrag component gesture recognizer, each drag component gesturerecognizer monitoring movement of a respective input. In the pinchgesture recognizer example, the parallel combiner requires success ofthe first pan gesture recognizer (e.g., based on a first touch inputbeing detected) concurrent with success of the second pan gesturerecognizer (e.g., based on a second touch input being detectedconcurrently with the first touch input). An example parallel combineris described herein with reference to FIGS. 5M-5Q.

In some embodiments, the third component gesture recognizer is (734) asequential combiner, and the third requirement requires, in order forthe third component gesture recognizer to succeed, success of the firstcomponent gesture recognizer and, after the first component gesturerecognizer succeeds, success of the second component gesture recognizer.In other words, the sequential combiner requires that its childcomponent gesture recognizers succeed one after another in order for thesequential component gesture recognizer to succeed. For example, a draggesture recognizer for recognizing a drag gesture that requires a longpress followed by movement of the input may be assembled using asequential combiner that has a long press gesture recognizer as itsfirst child and a pan gesture recognizer as its second child. In someembodiments, success of the sequential combiner requires the latercomponent gesture recognizer to succeed after the earlier componentgesture recognizer has succeeded and ended. In some embodiments, successof the sequential combiner still occurs where the later componentgesture recognizer succeeds after the earlier component gesturerecognizer succeeds but before the earlier component gesture recognizerhas ended. In some embodiments, the third requirement further requiresthat the second component gesture recognizer succeed within a predefinedamount of time (e.g., a timeout period) from the end of the firstcomponent gesture recognizer.

In some embodiments, a repeating component gesture recognizer is similarto a sequential component gesture recognizer in requiring sequentialsuccess of its child gesture recognizers, except that the repeatingcomponent gesture recognizer has a single child component gesturerecognizer that is reused or re-instantiated. In some embodiments, thechild component gesture recognizer(s) of a repeating combiner arecreated sequentially (e.g., because the two child component gesturerecognizers are a same type of component gesture recognizer (e.g.,distinct instances of a same component gesture recognizer)). In someembodiments, a first child component gesture recognizer of the repeatingcombiner is created and associated with the repeating combiner, and usedto process inputs and, after the first child succeeds and ends, thefirst child component gesture recognizer is destroyed, or removed fromthe gesture recognizer, and a second child component gesture recognizer(e.g., a second instance of the same type of component gesturerecognizer as the first child) is created and associated with therepeating combiner, and subsequently used to process inputs.) An examplerepeating component gesture recognizer is described above with referenceto repeater 522 in double-tap gesture recognizer 520, FIGS. 5G-5L.

Providing a sequential or repeating combiner that requires success, inturn, of multiple (child) gesture recognizers or component gesturerecognizers allows for the formation of composite gestures through reuseof (or using instances of) such gesture recognizers or component gesturerecognizers. This improves the variety of gestures that can berecognized while reducing the additional computation load typicallyimposed by monolithic gesture recognizers for increasingly diverse andcomplex gestures. This, in turn, improves device responsiveness andreduces latency, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the first requirement of the first componentgesture recognizer requires (736) that values of a parameter thatdescribes the input (e.g., any of location, distance moved, timestamp,duration, intensity) satisfy a specified threshold (e.g., the firstrequirement requires that the parameter value not exceed a maximumthreshold, and/or the first requirement requires that the parametervalue meet a minimum threshold, as described herein with reference toFIGS. 5A-5F). In some embodiments, the gesture recognizer includes afourth component gesture recognizer that determines the values of theparameter that describes the input. In some embodiments, monitoring theinput using the gesture recognizer includes monitoring the input usingthe fourth component gesture recognizer to determine the values of theparameter associated with the fourth component gesture recognizer, andthe method includes conveying the parameter values determined using thefourth component gesture recognizer to the first component gesturerecognizer for determining whether the first requirement is met. Using acomponent gesture recognizer that extracts particular information aboutan input and conveys the extracted information to another componentgesture recognizer that determines whether a respective requirement forrecognizing a gesture is met (e.g., based on the parameter value(s))makes available information that is needed to process an input withoutincreasing the computational load on the component gesture recognizerthat is responsible for making the determination of whether itsrespective requirement is satisfied. This improves device responsivenessand reduces latency, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the gesture recognizer is (738) a tap gesturerecognizer (e.g., tap gesture recognizer 500, FIG. 5A, which isdescribed in more detail herein with respect to FIGS. 5A-5F). In someembodiments, the first component gesture recognizer is a distancecomponent gesture recognizer that stores an initial location of theinput corresponding to a point in time when the input was first detectedand receives a current location of the input at a respective point intime. In some embodiments, the distance component gesture recognizerreceives the current location of the input from a component gesturerecognizer that identifies information about the input (e.g., an inputevent) that includes location information. In some embodiments, thedistance component gesture recognizer extracts the current location ofthe input from information about the input (e.g., an input event)conveyed to the distance component gesture recognizer). In someembodiments, the first requirement defined by the first componentgesture recognizer requires that a distance between the initial locationof the input and the current location of the input be within a thresholddistance. In some embodiments, the first component gesture recognizerdetermines whether the input satisfies the first requirement.

In some embodiments, the second component gesture recognizer is a(maximum) duration component gesture recognizer that stores an initialtimestamp corresponding to the point in time when the input was firstdetected and receives a current timestamp corresponding to therespective (e.g., current) point in time. In some embodiments, theduration component gesture recognizer receives the current timestamp ofthe input from a component gesture recognizer that identifiesinformation about the input (e.g., an input event) that includestimestamp information. In some embodiments, the duration componentgesture recognizer extracts the current timestamp of the input frominformation about the input (e.g., an input event) conveyed to theduration component gesture recognizer. In some embodiments, the secondrequirement defined by the second component gesture recognizer requiresthat an amount of time between the initial timestamp and the currenttimestamp be within a threshold (e.g., a predefined threshold) amount oftime. In some embodiments, the second component gesture recognizerdetermines whether the input satisfies the second requirement.

In some embodiments, the tap gesture recognizer further includes alocation component gesture recognizer that determines that the input hasa current location at the respective point in time (e.g., a spatialevent listener). In some embodiments, the tap gesture recognizer furtherincludes a first gating combiner that requires success of the secondcomponent gesture recognizer and success of the location componentgesture recognizer in order to succeed. In some embodiments, the tapgesture recognizer further includes a second gating combiner thatrequires success of the first gating combiner and success of the firstcomponent gesture recognizer in order to succeed. In some embodiments,the tap gesture recognizer further includes a pausing component gesturerecognizer that prevents success of the tap gesture recognizer while anyother gesture recognizer or component gesture recognizer having a higherpriority than the tap gesture recognizer is actively processing theinput (and has not yet failed).

In some embodiments, the gesture recognizer is a double-tap gesturerecognizer. In some embodiments, the double-tap gesture recognizerincludes a repeating component gesture recognizer that includes a tapgesture recognizer (e.g., all of the component gesture recognizers ofthe tap gesture recognizer, as described herein). In some embodiments,the repeating component gesture recognizer conveys information to andreceives processing results from the root node component gesturerecognizer of the tap gesture recognizer. In some embodiments, arepeating component gesture recognizer requires repeated success of theincluded gesture recognizer or component gesture recognizer. In someembodiments, the repeating component gesture recognizer defines a numberof times that the included gesture recognizer or component gesturerecognizer must succeed in order for the repeating component gesturerecognizer to succeed (e.g., two times, three times, four times, etc.).In some embodiments, the repeating component gesture recognizer definesa timing requirement, such as a maximum permitted delay betweensuccesses of the included gesture recognizer. In one example, therepeating component gesture recognizer in the double-tap gesturerecognizer requires the included tap gesture recognizer to succeed twotimes; in such an example, the repeating component gesture recognizermay optionally require that the tap gesture recognizer succeed a secondtime within a predefined time since the tap gesture recognizer succeededthe first time.

In some embodiments, the gesture recognizer is a pan gesture recognizer,where the pan gesture recognizer includes a pan event listener (e.g., acomponent gesture recognizer that identifies information about the inputthat indicates that the input has moved (e.g., without requiring thatthe information about the input indicate a current location of theinput)).

In some embodiments, the gesture recognizer is a long-press gesturerecognizer. In some embodiments, the long-press gesture recognizer issimilar to a tap gesture recognizer, except that the long-press gesturerecognizer includes a minimum duration component gesture recognizerinstead of a maximum duration component gesture recognizer.Specifically, in some embodiments the long-press gesture recognizerincludes a location component gesture recognizer (e.g., a spatial eventlistener) as described herein. In some embodiments, the long-pressgesture recognizer further includes a distance component gesturerecognizer that stores an initial location of the input corresponding toa point in time when the input was first detected and receives a currentlocation of the input at a respective point in time. The distancecomponent gesture recognizer defines a requirement for recognition of along-press gesture that a distance between the initial location of theinput and the current location of the input be within a thresholddistance.

In some embodiments, the long-press gesture recognizer further includesa minimum duration component gesture recognizer that stores an initialtimestamp corresponding to the point in time when the input was firstdetected and receives a current timestamp corresponding to therespective point in time. In some embodiments, the minimum durationcomponent gesture recognizer receives the current timestamp of the inputfrom a component gesture recognizer that identifies information aboutthe input that includes timestamp information. In some embodiments, theminimum duration component gesture recognizer extracts the currenttimestamp of the input from information about the input conveyed to theminimum duration component gesture recognizer. The minimum durationcomponent gesture recognizer defines a requirement for recognition of along-press gesture that an amount of time between the initial timestampand the current timestamp be at least a threshold (e.g., a predefinedthreshold) amount of time.

In some embodiments, the long-press gesture recognizer includes a firstgating combiner that requires success of the location gesture recognizerand success of the minimum duration component gesture recognizer inorder to succeed. In some embodiments, the long-press gesture recognizerincludes a second gating combiner that requires success of the firstgating combiner and success of the distance component gesture recognizerin order to succeed.

In some embodiments, the gesture recognizer is a pinch gesturerecognizer, where the pinch gesture recognizer includes a first dragcomponent gesture recognizer that listens for events with locationinformation and determines movement information based on the locationinformation, and a second drag component gesture recognizer that listensfor events with location information and determines movement informationbased on the location information. In some embodiments, the pinchgesture recognizer includes a parallel combiner that associates thefirst drag component gesture recognizer with a first input (e.g., afirst contact on a touch-sensitive surface) and that associates thesecond drag component gesture recognizer with a second input (e.g., asecond contact on the touch-sensitive surface). In some embodiments, theparallel combiner conveys information about the first input to the firstdrag component gesture recognizer but not the second drag componentgesture recognizer, and receives state information and values ofparameters that describe the first input from the first drag componentgesture recognizer. In some embodiments, the parallel combiner conveysinformation about the second input to the second drag component gesturerecognizer but not the first drag component gesture recognizer, andreceives state information and values of the parameters that describethe second input from the second drag component gesture recognizer. Insome embodiments, the pinch gesture recognizer includes a pinchcomponent gesture recognizer that receives the state information andparameter values for both the first input and the second input anddetermines, based on the state information and parameter values, a scalevalue (e.g., for zooming a displayed user interface element). An examplepinch gesture recognizer is illustrated in and described herein withreference to FIGS. 5M-5Q.

In some embodiments, the gesture recognizer is a rotate gesturerecognizer. In some embodiments, a rotate gesture recognizer is similarto a pinch gesture recognizer, except that the rotate gesture recognizerincludes a rotate component gesture recognizer instead of the pinchcomponent gesture recognizer. In some embodiments, the rotate componentgesture recognizer receives the state information and parameter values(e.g., location and movement information) for both the first input andthe second input and determines, based on the state information andparameter values, an angle (e.g., for rotating a displayed userinterface element) instead of a scale. Like the pinch gesturerecognizer, the rotate gesture recognizer further includes a first dragcomponent gesture recognizer that listens for events with locationinformation and determines movement information based on the locationinformation, a second drag component gesture recognizer that listens forevents with location information and determines movement informationbased on the location information, and a parallel combiner thatassociates the first drag component gesture recognizer with a firstinput (e.g., a first contact on a touch-sensitive surface) and thatassociates the second drag component gesture recognizer with a secondinput (e.g., a second contact on the touch-sensitive surface).

With respect to any gesture recognizer, including any of theaforementioned example gesture recognizers, a user (e.g., an applicationdeveloper) may add or remove modules to or from a gesture recognizer, ordevelop a modified version of any respective component gesturerecognizer in the gesture recognizer and replace the respectivecomponent gesture recognizer with the modified version, so as tocustomize the gesture recognizer and thereby customize the requirementsfor recognition of a gesture by the gesture recognizer.

It should be understood that the particular order in which theoperations in FIGS. 7A-7E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800 and 900) are also applicable in an analogous manner tomethod 700 described above with respect to FIGS. 7A-7E. For example, theinputs, states, values, user interfaces, component gesture recognizers,gesture recognizers, views, and view hierarchies described above withreference to method 700 optionally have one or more of thecharacteristics of the inputs, states, values, user interfaces,component gesture recognizers, gesture recognizers, views, and viewhierarchies described herein with reference to other methods describedherein (e.g., methods 800 and 900). For brevity, these details are notrepeated here.

FIGS. 8A-8C are flow diagrams illustrating method 800 of generatinggesture recognition hierarchies from view hierarchies of views in a userinterface in accordance with some embodiments. Method 800 is performedat an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display (e.g., touch screen112, FIG. 1A, or display 340, FIG. 3), an input device (e.g., touchscreen 112, FIG. 1A, touchpad 355 or keyboard/mouse 350, FIG. 3), andoptionally one or more sensors to detect intensity of contacts with aninput device that includes a touch-sensitive surface (e.g., contactintensity sensor(s) 165, FIG. 1A). In some embodiments, the display is atouch-screen display with a touch-sensitive surface on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 800 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 800 provides an intuitive way for anelectronic device to prioritize gesture recognizers to use in processingan input directed to a user interface of an application based on a viewhierarchy that defines relationships between views in the user interfacewith which the gesture recognizers are associated. Forming a gesturerecognition hierarchy between gesture recognizers based on therelationships between their associated views as defined in the viewhierarchy facilitates processing inputs in a manner consistent with thedisplayed user interface and improves the responsiveness of the device,which in turn reduces latency. Reducing latency in responding to inputsreduces user mistakes when operating/interacting with the device, suchas duplicative or extraneous inputs made by the user while waiting forthe device to respond to the user's earlier input(s). Reducing thenumber and/or extent of the inputs from a user enhances the operabilityof the device and makes the user-device interface more efficient, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

The device displays (802), on the display, a user interface of anapplication (e.g., user interface 600, FIG. 6A). The user interfaceincludes (804) a plurality of views (e.g., views 602, 606, 612, and 616,FIG. 6A) arranged in a view hierarchy (e.g., view hierarchy 630, FIG.6A), which in some embodiments defines one or more relationships, suchas parent-child relationships, between the plurality of views in theview hierarchy. The view hierarchy defines a first relationship (e.g., aview-hierarchy relationship) between a first view (e.g., view 612, FIG.6A) and a second view (e.g., view 606, FIG. 6A) (e.g., the first view isa child view of the second view, the first view is a parent view of thesecond view, the first view and the second view are sibling views (bothchild views of a same parent view), etc.). The first view includes afirst gesture recognizer (e.g., first tap gesture recognizer 614, FIG.6A), and the second view includes a second gesture recognizer (e.g.,scroll gesture recognizer 608, FIG. 6A).

The device detects (806), via the input device, an input (e.g., a touchinput on the touch-sensitive surface) at a first location thatcorresponds to the displayed user interface.

The device processes (808) the input using a gesture recognitionhierarchy (e.g., gesture recognition hierarchy 640) that includes thefirst gesture recognizer and the second gesture recognizer. A secondrelationship (e.g., a gesture-dependency relationship) between the firstgesture recognizer and the second gesture recognizer (in the gesturerecognition hierarchy) is determined based on the first relationshipbetween the first view and the second view in the view hierarchy. Insome embodiments, the gesture recognition hierarchy is formed inresponse to detecting an input (e.g., touch input 620), and based on adetermination as to which view in the view hierarchy is the hit view(e.g., based on a determination that view 612 is the hit view). In someembodiments, the relationships between gesture recognizers in thegesture recognition hierarchy are defined based on the relationshipsbetween the views (corresponding to each gesture recognizer) in the viewhierarchy with respect to the hit view, as described herein withreference to FIG. 6A.

In some embodiments, one or more views in the view hierarchy, other thanthe first view and the second view, include (810) respective gesturerecognizers, and the gesture recognition hierarchy includes therespective gesture recognizers of the one or more other views.Specifically, in some embodiments, the view hierarchy includes a thirdview that includes a third gesture recognizer (e.g., view 602 thatincludes long press gesture recognizer 604, FIG. 6A), and the gesturerecognition hierarchy includes the third gesture recognizer (e.g.,gesture recognition hierarchy 640 includes long press gesture recognizer604, FIG. 6A). In some embodiments, the gesture recognition hierarchyincludes a respective gesture recognizer of a respective view in theview hierarchy without regard to whether the respective view correspondsto the first location (e.g., as described herein with reference tosecond tap gesture recognizer 618 of view 616, FIG. 6A). In someembodiments, the view hierarchy includes a hit view, determined based onthe first location, and a set of views that are parent views of the hitview, and the gesture recognition hierarchy includes (in someembodiments only) respective gesture recognizers in the hit view and inthe parent views of the hit view. In some embodiments, the gesturerecognition hierarchy includes gesture recognizers of all views in theview hierarchy. Including, in the gesture recognition hierarchy, gesturerecognizers of (all) other views in the view hierarchy facilitatescomprehensive gesture processing that considers all possible gesturesassociated with a displayed user interface of an application on thedevice when processing inputs to the device. This improves deviceresponsiveness and reduces latency, thereby enhancing the operability ofthe device and making the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome and by reducing usermistakes when operating/interacting with the device).

In some embodiments, the device identifies (812) a subset of views inthe view hierarchy that correspond to the first location, where theidentified subset includes the first view and the second view, and wherethe gesture recognition hierarchy includes the respective gesturerecognizers of the identified subset of views (e.g., as described hereinwith reference to gesture recognition hierarchy 640, FIG. 6A).Specifically, in some embodiments, the view hierarchy includes a thirdview that includes a third gesture recognizer, where the third view doesnot correspond to the first location, and the gesture recognitionhierarchy does not include the third gesture recognizer of the thirdview. In some embodiments, only gesture recognizers of views in the viewhierarchy that correspond to the first location are candidates forrecognizing an input detected at the first location. In someembodiments, the gesture recognition hierarchy includes gesturerecognizers of views that correspond to the first location and does notinclude gesture recognizers of views that do not correspond to the firstlocation. In some embodiments, views that correspond to the firstlocation include a hit view, which is a lowest level view in the viewhierarchy that corresponds to the first location and optionally, meetspredefined criteria (e.g., includes at least one gesture recognizer, orincludes at least one gesture recognizer capable of recognizing aninput). In some embodiments, views that correspond to the first locationalso include one or more parent views of the hit view, and in someembodiments all parent views of the hit view. Including, in the gesturerecognition hierarchy, gesture recognizers of (only) a subset of viewsin the view hierarchy that are associated with the location at which aninput is detected facilitates gesture processing that considers gesturesthat are more likely to be relevant to the detected input withoutimposing the additional burden of considering gestures that are notassociated with the location and thus less likely to be relevant to thedetected input. This reduces the computational load on the device whenprocessing inputs, which improves device responsiveness and reduceslatency, thereby enhancing the operability of the device and making theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the view hierarchy includes (814) one or more viewsthat do not correspond to the first location, where the one or moreviews include one or more gesture recognizers, and the gesturerecognition hierarchy does not include the one or more gesturerecognizers of the one or more views that do not correspond to the firstlocation (e.g., as described herein with reference to second tap gesturerecognizer 618 of view 616, FIG. 6A). Including, in the gesturerecognition hierarchy, gesture recognizers of (only) a subset of viewsin the view hierarchy that are associated with the location at which aninput is detected facilitates gesture processing that considers gesturesthat are more likely to be relevant to the detected input withoutimposing the additional burden of considering gestures that are notassociated with the location and thus less likely to be relevant to thedetected input. This reduces the computational load on the device whenprocessing inputs, which improves device responsiveness and reduceslatency, thereby enhancing the operability of the device and making theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the gesture recognition hierarchy (sometimes calleda gesture recognition tree) includes (816) a component gesturerecognizer (e.g., an exclusive combiner, such as exclusive combiner 642,FIG. 6A) that defines the second relationship between the first gesturerecognizer and the second gesture recognizer by requiring that the firstgesture recognizer fail in order for the second gesture recognizer tosucceed. Using a separate component gesture recognizer (e.g., acombiner) to define and monitor a relationship between first and secondgesture recognizers in a gesture recognition hierarchy improves theability of an electronic device to distinguish between differentgestures without increasing the computational load on the first andsecond gesture recognizers, which improves device responsiveness andreduces latency. In addition, using the separate component gesturerecognizer reduces the need for case-by-case modification of the firstand second gesture recognizers, which provides consistency in gesturerecognition. These benefits enhance the operability of the device andmake the user-device interface more efficient (e.g., by helping the userto achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the gesture recognition hierarchy includes (818) acomponent gesture recognizer that defines the second relationshipbetween the first gesture recognizer and the second gesture recognizerin the gesture recognition hierarchy. In some embodiments, processingthe input using the gesture recognition hierarchy includes: receiving,at the gesture recognition hierarchy, information that describes theinput; conveying the information that describes the input to thecomponent gesture recognizer; and conveying the information thatdescribes the input from the component gesture recognizer to at leastone of the first gesture recognizer and the second gesture recognizerbased on the second relationship between the first gesture recognizerand the second gesture recognizer. In some embodiments, processing theinput using the gesture recognition hierarchy also includes, inaccordance with a determination that the information that describes theinput is conveyed to the first gesture recognizer, processing theinformation that describes the input using the first gesture recognizer.In some embodiments, processing the input using the gesture recognitionhierarchy further includes, in accordance with a determination that theinformation that describes the input is conveyed to the second gesturerecognizer, processing the information that describes the input usingthe second gesture recognizer.

Alternatively, in some embodiments, the device conveys, at a first time,the information that describes the input from the component gesturerecognizer to the first gesture recognizer but not the second gesturerecognizer, and at a second time after the first time, in accordancewith a determination that the first gesture recognizer has failed torecognize the input, the device conveys the information that describesthe input from the component gesture recognizer to the second gesturerecognizer. For example, as explained above with respect to operation718 of method 700, some combiners convey the information that describesthe input (e.g., one or more input events) to all of their childcomponent gesture recognizers based on information conveyance rules forthat combiner or combiner type. Other combiners convey the informationto only some of their child component gesture recognizers, based oninformation conveyance rules for that combiner or combiner type, eitherby conveying information about a first input of multiple inputs only toa first child and information about a second input of the multipleinputs only to a second child, or by conveying information about one ormore inputs to a second child only after the first child succeeds orotherwise has completed processing the information.

Conveying information from a combiner in a gesture recognition hierarchyto at least one of first and second gesture recognizers based on therelationship between the first and second gesture recognizers defined bythe combiner reduces unnecessary processing of an input by gesturerecognizers that are not currently relevant to the input. This reducesthe computational load on the device, which improves deviceresponsiveness and reduces latency, thereby enhancing the operability ofthe device and making the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome and by reducing usermistakes when operating/interacting with the device).

In some embodiments, processing the information that describes the inputusing the first gesture recognizer determines (820) a current state ofthe first gesture recognizer, and processing the information thatdescribes the input using the second gesture recognizer determines acurrent state of the second gesture recognizer. In some embodiments, thedevice conveys the current state of the first gesture recognizer fromthe first gesture recognizer to the component gesture recognizer;conveys the current state of the second gesture recognizer from thesecond gesture recognizer to the component gesture recognizer; andprocesses, using the component gesture recognizer, the information thatdescribes the input, the current state of the first gesture recognizer,and the current state of the second gesture recognizer, to determine acurrent state of the component gesture recognizer. In some embodiments,different component gesture recognizers have different informationprocessing rules, and thus how the states are processed to determine thecurrent state is determined by the processing rules for the componentgesture recognizer type of the component gesture recognizer. Examples ofdetermining states of gesture recognizers based on states of componentgesture recognizers are described herein with reference to FIGS. 5A-5Q.Determining the state of a component gesture recognizer that defines arelationship between two gesture recognizers based on the states of thegesture recognizers enables more complex input processing withoutincreasing the amount of processing required at the gesture recognizers,which simplifies event handling and reduces the computational load onthe device when processing inputs. This improves device responsivenessand reduces latency, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome and by reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the first view includes (822) a third gesturerecognizer, and the gesture recognition hierarchy includes the thirdgesture recognizer and a component gesture recognizer that defines athird relationship between the first gesture recognizer and the thirdgesture recognizer in the gesture recognition hierarchy. In someembodiments, the device determines a gesture recognition state of thefirst view by performing a plurality of operations. In some embodiments,the operations include conveying information that describes the input tothe component gesture recognizer, the first gesture recognizer, and thethird gesture recognizer. In some embodiments, the operations includeprocessing the information that describes the input using the firstgesture recognizer to determine a current state of the first gesturerecognizer, and conveying the current state of the first gesturerecognizer from the first gesture recognizer to the component gesturerecognizer. In some embodiments, the operations also include processingthe information that describes the input using the third gesturerecognizer to determine a current state of the third gesture recognizer,and conveying the current state of the third gesture recognizer from thethird gesture recognizer to the component gesture recognizer. In someembodiments, the operations further include processing, using thecomponent gesture recognizer, the information that describes the input,the current state of the first gesture recognizer, and the current stateof the third gesture recognizer, to determine the gesture recognitionstate of the first view. For example, the gesture recognition state ofhit view 612 in FIG. 6A is determined based on the (overall) processingresults of gesture recognition hierarchy 640.

In some embodiments, if a view has only one gesture recognizer, then the(current) gesture recognition state of the view is the (current) gesturerecognition state of the one gesture recognizer. In some embodiments, ifa view has two or more gesture recognizers, then the two or more gesturerecognizers are arranged in a gesture recognition hierarchy (e.g., abranch of a larger gesture recognition hierarchy that also includesgesture recognizers for other views) using one or more combiners thatdefines priority, or simultaneity, between the two or more gesturerecognizers. In some embodiments, the gesture recognition state of theview is determined by the one or more combiners (e.g., by a combiner ata highest (root) node of the gesture recognition hierarchy for the view)based on the (current) states of the two or more gesture recognizers(e.g., a respective node determines its current state based onrespective states of its child nodes in the gesture recognitionhierarchy). For example, the gesture recognition state of view 606 inFIG. 6A is determined based on the processing results of simultaneouscombiner 646 which defines the relationship between the two gesturerecognizers, scroll gesture recognizer 608 and pinch gesture recognizer610, of view 616.

Determining the gesture recognition state of a view based on the stateof a component gesture recognizer that defines a relationship betweentwo gesture recognizers in the view, where the state of the componentgesture recognizer is in turn based on the states of the gesturerecognizers, enables more complex input processing and improves theability of the device to distinguish between different gestures withoutincreasing the amount of processing required at the gesture recognizers.This simplifies event handling and reduces the computational load on thedevice when processing inputs, which in turn improves deviceresponsiveness and reduces latency, thereby enhancing the operability ofthe device and making the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome and by reducing usermistakes when operating/interacting with the device).

It should be understood that the particular order in which theoperations in FIGS. 8A-8C have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 900) are also applicable in an analogous manner tomethod 800 described above with respect to FIGS. 8A-8C. For example, theinputs, states, values, user interfaces, component gesture recognizers,gesture recognizers, views, and view hierarchies described above withreference to method 800 optionally have one or more of thecharacteristics of the inputs, states, values, user interfaces,component gesture recognizers, gesture recognizers, views, and viewhierarchies described herein with reference to other methods describedherein (e.g., methods 700 and 900). For brevity, these details are notrepeated here.

FIGS. 9A-9B are flow diagrams illustrating method 900 of processinginputs using gesture recognizers to which values of parameters thatdescribe the inputs have been associated in accordance with someembodiments. Method 900 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) withan input device (e.g., touch screen 112, FIG. 1A, touchpad 355 orkeyboard/mouse 350, FIG. 3), optionally a display (e.g., touch screen112, FIG. 1A, or display 340, FIG. 3), and optionally one or moresensors to detect intensity of contacts with an input device thatincludes a touch-sensitive surface (e.g., contact intensity sensor(s)165, FIG. 1A). In some embodiments, the display is a touch-screendisplay with a touch-sensitive surface on or integrated with thedisplay. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 900 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 900 provides an intuitive way for anelectronic device to monitor an input using a gesture recognition tree(sometimes called a gesture recognition hierarchy) in which multiplegesture recognizers are arranged. Transferring values of parameters thatdescribe the input between gesture recognizers in the tree provides thegesture recognizers with information about the input that is needed forprocessing inputs without requiring each gesture recognizer toseparately determine the information, which reduces the computationalload on the device when processing inputs, thereby improving deviceresponsiveness and reducing latency. Reducing latency in responding toinputs reduces user mistakes when operating/interacting with the device,such as duplicative or extraneous inputs made by the user while waitingfor the device to respond to the user's earlier input(s). Reducing thenumber and/or extent of the inputs from a user enhances the operabilityof the device and makes the user-device interface more efficient, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

The device detects (902) an input via the input device (e.g., a touchinput on the touch-sensitive surface).

In response to detecting the input, the device monitors (904) the inputusing a gesture recognition tree having a plurality of nodes (e.g., agesture recognizer assembled from a plurality of component gesturerecognizers) (e.g., any gesture recognizer or gesture recognitionhierarchy described herein with reference to FIGS. 5A-5Q and 6A-6C).Each respective node of the gesture recognition tree corresponds (906)to a respective gesture recognizer (e.g., a gesture recognizer thatincludes a plurality of component gesture recognizers) or a respectivecomponent gesture recognizer (e.g., a combiner). In addition, one ormore nodes include (e.g., store) one or more parameters that describethe input (e.g., location of initial detection of the input, currentlocation, distance traveled (determined based on current location andinitial location), velocity, contact intensity, initial timestamp (e.g.,when the input was first detected), current timestamp).

Monitoring the input using the gesture recognition tree includes (908):processing the input using a first node of the plurality of nodes,including determining a value of a first parameter of the one or moreparameters; conveying the first parameter from the first node to asecond node of the plurality of nodes; and processing the input usingthe second node, including determining, based on the first parameter,whether the input satisfies a gesture recognition requirement defined bythe second node. In some embodiments, the gesture recognitionrequirement defined by the second node is one of a set of gesturerecognition criteria defined by the gesture recognition tree (e.g., agesture recognizer). An example of processing inputs to determine valuesof parameters that describe the inputs and conveying the values to othernodes for further processing of the inputs is described herein withreference to FIGS. 5M-5Q.

In some embodiments, the one or more parameters that describe the inputinclude (910) one or more of: a location at which the input wasinitially detected, a current location of the input, a distance traveledby the input (e.g., by a contact across a touch-sensitive surface), avelocity of the input (e.g., an instantaneous velocity, whether detectedoutright or derived from location and time information), a contactintensity (e.g., of a touch input), an initial timestamp correspondingto a time at which the input was first detected, and a currenttimestamp. For example, FIGS. 5M-5Q illustrate examples of conveyedparameters that include current timestamp, current velocity, initiallocation, and current location.

In some embodiments, the first parameter is (912) a location of theinput, and the gesture recognition requirement defined by the secondnode requires that a distance between an initial location of the inputand a current location of the input satisfy a threshold distance. Insome embodiments, the threshold distance is satisfied when the distancebetween the initial location and the current location exceeds athreshold distance (e.g., the input must move at least a minimumdistance in order for the gesture recognition requirement defined by thesecond node to be satisfied, and for a gesture associated with thesecond node to be recognized). In some embodiments, the thresholddistance is satisfied when the distance between the initial location andthe current location is within a threshold distance (e.g., the inputmust not move more than a maximum distance in order for the gesturerecognition requirement defined by the second node to be satisfied, andfor a gesture associated with the second node to be recognized). In someembodiments, processing the input using the first node includesdetermining, using the first node, the current location of the input. Insome embodiments, processing the input using the second node includesdetermining, using the second node, whether the distance between theinitial location of the input (e.g., stored by the second node) and thecurrent location of the input conveyed from the first node satisfies thethreshold distance.

In some embodiments, the first parameter is (914) a timestampcorresponding to a respective point in time at which the input isdetected, and the gesture recognition requirement defined by the secondnode requires that an amount of time between an initial timestampcorresponding to a first point in time at which the input was firstdetected and a current timestamp corresponding to a second point in timeat which the input is detected satisfy a threshold amount of time. Insome embodiments, the threshold amount of time is satisfied when theamount of time between the initial timestamp and the current timestampexceeds a threshold amount of time (e.g., the input must continue to bedetected (e.g., remain on the touch-sensitive surface, for a touchinput) for at least a minimum amount of time in order for the gesturerecognition requirement defined by the second node to be satisfied, andfor a gesture associated with the second node to be recognized). In someembodiments, the threshold amount of time is satisfied when the amountof time between the initial timestamp and the current timestamp iswithin a threshold amount of time (e.g., the input must not continue tobe detected (e.g., remain on the touch-sensitive surface) for more thana maximum amount of time in order for the gesture recognitionrequirement defined by the second node to be satisfied, and for agesture associated with the second node to be recognized). In someembodiments, processing the input using the first node includesdetermining, using the first node, the current timestamp correspondingto the second point in time at which the input is detected. In someembodiments, processing the input using the second node includesdetermining, using the second node, whether the amount of time betweenthe initial timestamp of the input (e.g., stored by the second node) andthe current timestamp of the input conveyed from the first nodesatisfies the threshold amount of time.

In some embodiments, the device processes (916) the input using one ormore of the plurality of nodes in the gesture recognition tree todetermine values of the one or more parameters without regard to whethera gesture has been recognized by the gesture recognition tree (e.g., asdescribed herein with reference to FIG. 5N, which illustrates the statesand values of pinch gesture recognizer 530 before a pinch gesture hasbeen recognized). In some embodiments, values of the one or moreparameters are determined prior to recognition of a gesture by thegesture recognition tree. For example, the values are determined evenwhen a state of the gesture recognizer tree (e.g., an overall statedetermined based on respective states of the nodes in the gesturerecognition tree, as described above with reference to method 700) is astate other than a gesture recognition state (e.g., a predefined“possible” state, which indicates that a particular gesture to berecognized by the gesture recognizer is possible). Determining values ofparameters that describe an input while processing the input, withoutregard to whether a gesture has been recognized, reduces delay inprocessing the input and helps the device recognize gestures morequickly. Improving responsiveness of the device enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to achieve an intended outcome more quickly and byreducing user mistakes when operating/interacting with the device).

In some embodiments, in response to detecting the input, the devicereceives (918), at the gesture recognition tree, first information thatdescribes the input, where the value of the first parameter isdetermined from the first information, and where determining whether theinput satisfies the gesture recognition requirement defined by thesecond node includes comparing the value of the first parameter to aprior value determined from second information received at the gesturerecognition tree prior to receiving the first information (e.g., asdescribed herein with reference to FIGS. 5M-5Q, pinch gesture recognizer530 compares current locations of respective inputs to initial locationsto determine whether the inputs satisfy pinch gesture requirements).Determining whether an input satisfies a particular gesture recognitionrequirement by comparing a current value of a parameter that describesthe input to a previous (e.g., initial) value of the parameter providesan efficient way to monitor the input over time, which reduces thecomputational load on the device when processing inputs. This improvesdevice responsiveness and reduces latency, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome andby reducing user mistakes when operating/interacting with the device).

It should be understood that the particular order in which theoperations in FIGS. 9A-9B have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 800) are also applicable in an analogous manner tomethod 900 described above with respect to FIGS. 9A-9B. For example, theinputs, states, values, user interfaces, component gesture recognizers,gesture recognizers, views, and view hierarchies described above withreference to method 900 optionally have one or more of thecharacteristics of the inputs, states, values, user interfaces,component gesture recognizers, gesture recognizers, views, and viewhierarchies described herein with reference to other methods describedherein (e.g., methods 700 and 800). For brevity, these details are notrepeated here.

The operations described above with reference to FIGS. 7A-7E, 8A-8C, and9A-9B are, optionally, implemented by components depicted in FIGS.1A-1B. For example, detection operations 702, 806, 902, monitoringoperations 704, 904, recognizing operations 708, and processingoperation 806 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 one ormore component event recognizers 181 to compare the event information torespective event definitions 184, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method, comprising: at an electronic devicewith a display and an input device; displaying, on the display, a userinterface of an application, wherein the user interface includes aplurality of views arranged in a view hierarchy, wherein the viewhierarchy defines a first relationship between a first view and a secondview, and wherein the first view includes a first gesture recognizer,and the second view includes a second gesture recognizer; detecting, viathe input device, an input at a first location that corresponds to thedisplayed user interface; and processing the input using a gesturerecognition hierarchy that includes the first gesture recognizer and thesecond gesture recognizer, wherein a second relationship between thefirst gesture recognizer and the second gesture recognizer is determinedbased on the first relationship between the first view and the secondview in the view hierarchy.
 2. The method of claim 1, wherein one ormore views in the view hierarchy, other than the first view and thesecond view, include respective gesture recognizers, and wherein thegesture recognition hierarchy includes the respective gesturerecognizers of the one or more other views.
 3. The method of claim 1,including identifying a subset of views in the view hierarchy thatcorrespond to the first location, wherein the identified subset includesthe first view and the second view, and wherein the gesture recognitionhierarchy includes the respective gesture recognizers of the identifiedsubset of views.
 4. The method of claim 3, wherein the view hierarchyincludes one or more views that do not correspond to the first location,wherein the one or more views include one or more gesture recognizers,and wherein the gesture recognition hierarchy does not include the oneor more gesture recognizers of the one or more views that do notcorrespond to the first location.
 5. The method of claim 1, wherein thegesture recognition hierarchy includes a component gesture recognizerthat defines the second relationship between the first gesturerecognizer and the second gesture recognizer by requiring that the firstgesture recognizer fail in order for the second gesture recognizer tosucceed.
 6. The method of claim 1, wherein the gesture recognitionhierarchy includes a component gesture recognizer that defines thesecond relationship between the first gesture recognizer and the secondgesture recognizer in the gesture recognition hierarchy, and whereinprocessing the input using the gesture recognition hierarchy includes:receiving, at the gesture recognition hierarchy, information thatdescribes the input; conveying the information that describes the inputto the component gesture recognizer; conveying the information thatdescribes the input from the component gesture recognizer to at leastone of the first gesture recognizer and the second gesture recognizerbased on the second relationship between the first gesture recognizerand the second gesture recognizer; in accordance with a determinationthat the information that describes the input is conveyed to the firstgesture recognizer, processing the information that describes the inputusing the first gesture recognizer; and in accordance with adetermination that the information that describes the input is conveyedto the second gesture recognizer, processing the information thatdescribes the input using the second gesture recognizer.
 7. The methodof claim 6, wherein processing the information that describes the inputusing the first gesture recognizer determines a current state of thefirst gesture recognizer, processing the information that describes theinput using the second gesture recognizer determines a current state ofthe second gesture recognizer, and the method includes: conveying thecurrent state of the first gesture recognizer from the first gesturerecognizer to the component gesture recognizer; conveying the currentstate of the second gesture recognizer from the second gesturerecognizer to the component gesture recognizer; processing, using thecomponent gesture recognizer, the information that describes the input,the current state of the first gesture recognizer, and the current stateof the second gesture recognizer, to determine a current state of thecomponent gesture recognizer.
 8. The method of claim 1, wherein: thefirst view includes a third gesture recognizer; the gesture recognitionhierarchy includes the third gesture recognizer and a component gesturerecognizer that defines a third relationship between the first gesturerecognizer and the third gesture recognizer in the gesture recognitionhierarchy; and the method includes determining a gesture recognitionstate of the first view, including: conveying information that describesthe input to the component gesture recognizer, the first gesturerecognizer, and the third gesture recognizer; processing the informationthat describes the input using the first gesture recognizer to determinea current state of the first gesture recognizer, and conveying thecurrent state of the first gesture recognizer from the first gesturerecognizer to the component gesture recognizer; processing theinformation that describes the input using the third gesture recognizerto determine a current state of the third gesture recognizer, andconveying the current state of the third gesture recognizer from thethird gesture recognizer to the component gesture recognizer;processing, using the component gesture recognizer, the information thatdescribes the input, the current state of the first gesture recognizer,and the current state of the third gesture recognizer, to determine thegesture recognition state of the first view.
 9. An electronic device,comprising: a display; an input device; one or more processors; andmemory storing one or more programs, wherein the one or more programsare configured to be executed by the one or more processors, the one ormore programs including instructions for: displaying, on the display, auser interface of an application, wherein the user interface includes aplurality of views arranged in a view hierarchy, wherein the viewhierarchy defines a first relationship between a first view and a secondview, and wherein the first view includes a first gesture recognizer,and the second view includes a second gesture recognizer; detecting, viathe input device, an input at a first location that corresponds to thedisplayed user interface; and processing the input using a gesturerecognition hierarchy that includes the first gesture recognizer and thesecond gesture recognizer, wherein a second relationship between thefirst gesture recognizer and the second gesture recognizer is determinedbased on the first relationship between the first view and the secondview in the view hierarchy.
 10. The electronic device of claim 9,wherein one or more views in the view hierarchy, other than the firstview and the second view, include respective gesture recognizers, andwherein the gesture recognition hierarchy includes the respectivegesture recognizers of the one or more other views.
 11. The electronicdevice of claim 9, including identifying a subset of views in the viewhierarchy that correspond to the first location, wherein the identifiedsubset includes the first view and the second view, and wherein thegesture recognition hierarchy includes the respective gesturerecognizers of the identified subset of views.
 12. The electronic deviceof claim 11, wherein the view hierarchy includes one or more views thatdo not correspond to the first location, wherein the one or more viewsinclude one or more gesture recognizers, and wherein the gesturerecognition hierarchy does not include the one or more gesturerecognizers of the one or more views that do not correspond to the firstlocation.
 13. A computer readable storage medium storing one or moreprograms, the one or more programs comprising instructions, which, whenexecuted by an electronic device with a display and an input device,cause the device to: display, on the display, a user interface of anapplication, wherein the user interface includes a plurality of viewsarranged in a view hierarchy, wherein the view hierarchy defines a firstrelationship between a first view and a second view, and wherein thefirst view includes a first gesture recognizer, and the second viewincludes a second gesture recognizer; detect, via the input device, aninput at a first location that corresponds to the displayed userinterface; and process the input using a gesture recognition hierarchythat includes the first gesture recognizer and the second gesturerecognizer, wherein a second relationship between the first gesturerecognizer and the second gesture recognizer is determined based on thefirst relationship between the first view and the second view in theview hierarchy.
 14. The computer readable storage medium of claim 13,wherein one or more views in the view hierarchy, other than the firstview and the second view, include respective gesture recognizers, andwherein the gesture recognition hierarchy includes the respectivegesture recognizers of the one or more other views.
 15. The computerreadable storage medium of claim 13, including identifying a subset ofviews in the view hierarchy that correspond to the first location,wherein the identified subset includes the first view and the secondview, and wherein the gesture recognition hierarchy includes therespective gesture recognizers of the identified subset of views. 16.The computer readable storage medium of claim 15, wherein the viewhierarchy includes one or more views that do not correspond to the firstlocation, wherein the one or more views include one or more gesturerecognizers, and wherein the gesture recognition hierarchy does notinclude the one or more gesture recognizers of the one or more viewsthat do not correspond to the first location.